System and method for implementing media and media transfer between devices

ABSTRACT

A method to transfer control is presented. The method includes receiving a request to transfer control of a collaborative session from a first user equipment (UE). The method includes sending a request for the transfer of control of the collaborative session in response to the received request to a second UE, and receiving, in response to the sent request to the second UE, an indication of acceptance of the transfer of control of the collaborative session. The method includes sending a notification of status to the first UE of the control of the collaborative session in response to receiving, from the second UE, the indication of acceptance.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and incorporates by reference U.S.Provisional Patent Application No. 61/175,403 which has the same titleand was filed on May 4, 2009.

BACKGROUND

The present disclosure relates generally to media and/or controlfunction management for sessions in mobile communication systems andmore specifically to a system and method for implementing media and/orcontrol function transfer between devices.

As used herein, the term “device” can refer to the terms “mobilestation” (MS), “user agent,” or “user equipment” (UE) which can includeelectronic devices such as fixed and mobile telephones, personal digitalassistants, handheld or laptop computers, smartphones, printers, faxmachines, televisions, set top boxes, and other video display devices,home audio equipment and other home entertainment systems, homemonitoring and control systems (e.g., home monitoring, alarm systems andclimate control systems), enhanced home appliances such as computerizedrefrigerators and similar devices that have network communicationscapabilities. In some configurations, UE may refer to a mobile, wirelessdevice. Such UEs that are mobile, wireless devices may or may notinclude a memory module that is internal to the device or can beremoved, examples being but not limited to: a subscriber identity module(SIM) or a UICC card possibly including an ISIM application, CompactFlash, MicroSD, R-UIM etc. SIM/UICC functionality may also be providedfor by software downloadable SIM/UICC security software. The terms mayalso refer to devices that have similar capabilities but that are notreadily transportable, such as desktop computers, set-top boxes, TV,IPTV or network nodes. The term device also covers the term SIP UserAgent (UA) that can be fixed or mobile. When a UA is a network node, thenetwork node could act on behalf of another function such as a UA or afixed line device and simulate or emulate the UA or fixed line device.For example, for some UAs, the IMS SIP client that would typicallyreside on the device actually resides in the network and relays SIPmessage information to the device using optimized protocols. In otherwords, some functions that were traditionally carried out by a UA can bedistributed in the form of a remote UA, where the remote UA representsthe UA in the network. The term “UA” can also refer to any hardware orsoftware component that can terminate a communication session that couldinclude, but is not limited to, a SIP session. Also, the terms “useragent,” “UA,” “user equipment, “UE,” and “node” might be usedsynonymously herein. Those skilled in the art will appreciate that theseterms can be used interchangeably within the application.

A UE may operate in a wireless communication network that provides forhigh-speed data communications. For example, the UE may operate inaccordance with Global System for Mobile Communications (GSM) andGeneral Packet Radio Service (GPRS) technologies. Today, such a UE mayfurther operate in accordance with Enhanced Data rates for GSM Evolution(EDGE), or Enhanced GPRS (EGPRS) or Enhanced GPRS Phase 2 (EGPRS2).Other wireless networks that UEs may operate include but are not limitedto CDMA, UMTS, E-UTRAN, WiMax, and WLAN (e.g 802.11). UEs may alsooperate in fixed network environments such as xDSL, DOCSIS cablenetworks, ethernet or optical networks. Some UEs may be capable ofmultimode operation where they can operate on more than one accessnetwork technology either on a single access network at a time or insome devices using multiple access technologies simultaneously.

EDGE/EGPRS/EGPRS2 are examples of digital mobile communicationstechnology that allows for increased data transmission rate and improveddata transmission reliability. The network is often classified as a2.75G network technology. EDGE has been introduced into GSM networksaround the world since approximately 2003, initially in North America.EDGE/EGPRS/EGPRS2 may be used in any packet-switched application, suchas those involving an internet connection. High-speed data applications,such as video and other multimedia services, benefit from EGPRS'increased data capacity. A UE may also operate in other wirelesstechnologies such as but not limited to Wimax, Wifi, etc.

As communications network grow increasingly complex, networkinfrastructure is moving away from the telephony-based concept of asingle identity, such as a telephone number, that uniquely maps to asingle telephone line, cell phone or other UE. For example, SessionInitiation Protocol (SIP) and other related internet based communicationtechnologies support registering of multiple devices with a network,each device sharing the same user identity (for example, a SIP or TelUniform Resource Identifier (URI)), or a group of overlapping oridentical identities. This group of identities is called an ImplicitRegistration Set (IRS). In keeping with the evolution of communicationnetworks, SIP is also capable of support of various media typesincluding but not limited to text, data for applications, audio andvideo, etc within the same session established between a network and aUE. Those skilled in the art will appreciate that the devices/SIP UA'scan have different capabilities, such as small screen that supportsvideo or an IPTV that supports HDTV. It would therefore be advantageousif a session between 2 or more devices/SIP UA's started on a smallscreen that had a video and voice component could have its videocomponent moved to the HDTV when the user was near it. This capabilityis called Inter UE Transfer (IUT) and is defined in 3GPP TS 23.237 and3GPP TS 24.292.

To provide for effective operation of the network and associated devicesin IUT, PNM or other services like BlackBerry Unite, some networksinclude administrator or controller UEs having the capability to managethe devices or sessions that can be delivered within a group of targetUEs that are each correlated with a network server. In that case, theadministrator or controller UE may be configured to manage the operationof various features/parameters made available via one or more other UEs.In some cases, the controller function may be transferred from acontroller UE to another UE which has the capability of providingcontroller functionality. In some cases multiple UEs may act ascontroller. In some cases, a controller UE may implement PersonalNetwork Management (PNM) controller functionality. In some cases, a UEhas multiple User Agents, one per access network. Similarly, aadministrator or controller UA may be configured to manage the operationof various features or parameters made available via one or more otherUAs. An administrator or controller UA can also be an administrator orcontroller UE. In the following, the terms UE and UA are often usedinterchangeably, unless it is clear from the context.

SIP enables a UE to be configured such that it can be notified dependingon senders' identities for communication filtering and the diversion ofservices based upon which UE a communication is addressed to. Forexample a user may configure a call/communication forwarding service toallow a particular public user identity (such as a home phone number oremail address) to be provided to family members to reach a user directlyat the user's mobile phone and friends or family members may beforwarded to personal voicemail while co-workers are forwarded to anoffice phone which forwards ultimately to corporate voicemail.

As such, SIP allows a user to have consistent identities across multipleUEs wherein the UEs may include home phones, personal mobile phones,work phones, corporate mobile phones, vacation home phones, laptopcomputer voice-over-IP (VoIP) clients, fax machines, etc. The consistentpublic user identities also allow a user to be reachable at whichever UEthe user happens to be currently using. This flexibility minimizes thenecessity of maintaining a large list of device oriented contacts toidentify each user in an address book and having to decide which deviceis best when attempting to establish a communication—each user (and alltheir associated cell phone, home phones, computers, etc.) may beidentified by a single identification. As such, it is possible tocommunicate with someone using only a single identification with thenetwork and/or the terminating user determining the most appropriate UEfor use in contacting the individual.

In networks implementing SIP and having administrator or controller UEs,it is desirable to ensure that new sessions are to be established to UEshaving the best capability to handle the content, which may includevarious media types. It would not be most appropriate, for example, toaccept media including video content on a conventional office phoneeither having no means for displaying the video content or having a verysmall video screen when a television or computer screen/monitor isavailable for use by the user. Furthermore, when a UE is alreadyinvolved in a session that uses one or more media types and the UEreceives an invitation to add or modify one or more media types to thesession, a controller UE should be identified so that the user canrequest to transfer the new media type to a different UE that cansupport and process or render the new media type. For example, if a useris engaged in an audio session on the user's mobile phone and the userwishes to accept added video steaming media on another device, thecontroller UE provides the user with the ability to select anotherdevice, such as a Laptop PC, for receiving and displaying the addedvideo streaming media based on such as device capability and userpreference.

Additionally the user may use different devices for controllers of thesession during the time of the session. For example, a user may acceptthe session or one or more media components of the session on his mobilephone outside in the garden but then move inside the house and transferboth the audio and video components to his desktop computer and sincethe user wishes now to control the session from his desktop computer healso transfers control of the session from his mobile phone to hisdesktop computer. Finally, controller status functionality should onlybe transferred between certain member UEs capable of being thecontroller devices (e.g., basic televisions are unlikely to have thecapability to interact with the user to perform the controllerfunctionality) and authorized to receive the controller function by thenetwork. Accordingly, it is important to provide a secure mechanism todistribute and process transfer requests for the session, media, andcontroller functionality among a set of UEs that can potentially be usedby different subscribers (e.g., shared devices such as home phones andtelevisions).

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following brief description, taken in connection with theaccompanying drawings and detailed description, wherein like referencenumerals represent like parts.

FIG. 1 illustrates an example flow to transfer media and IUT controllerfunction between UEs associated with a network;

FIG. 2 illustrates an exemplary communications network for implementingthe present system for performing IUT media and/or controller functiontransfer between UEs connected to the network;

FIG. 3 illustrates an example flow for registering a UE with an IMSnetwork causing registration with an SCC AS;

FIG. 4 illustrates an exemplary allowed IUT List Management Object foridentifying one or more IUT-capable UEs which include controllee UE orboth controller UE and controllee UE;

FIGS. 5 a and 5 b illustrate the parameters and DDF of the exemplaryallowed IUT List MO shown in FIG. 4;

FIG. 6 illustrates an example flow for providing IUT controller functionto a UE where authorization is only required from a single controllerUE;

FIG. 7 illustrates an example flow for providing IUT controller functionto a UE where authorization is only required from more than onecontroller UEs;

FIG. 8 illustrates an example flow for transferring media-A andcontroller function to a UE as requested by an IUT-controller UE;

FIG. 9 illustrates an example flow for transferring media-A andcontroller function from UE-1 to UE-2, the incoming session requestincludes a controller function identifier and is delivered over the Gmreference point and the media-A is transmitted via a circuit-switchednetwork;

FIG. 10 illustrates an example flow for transferring media-A andcontroller function from UE-1 to UE-2, where the incoming sessionrequest includes a controller function identifier and is delivered overthe I1 reference point and the media-A is transmitted via a CS network;

FIG. 11 illustrates multiple UEs associated with a user, collaborativesessions are established between a subset of the UEs;

FIGS. 12 a and 12 b illustrate example flows for terminatingcollaborative session establishment when receiving a session invitationrequest;

FIG. 13 illustrates an example flow for transferring IUT Controllerfunctionality from a first PS UE to a second PS UE, wherein the firstand second UEs may use the same bearer or different bearers;

FIG. 14 is an illustration of an alternative message flow formedia/controller functionality transfer to another UE withinCollaborative Session using Gm reference point;

FIG. 15 is an illustration of an alternative message flow formedia/controller functionality transfer to another UE withinCollaborative Session using the I1 reference point;

FIG. 16 is an illustration of an alternative message flow for ControllerInitiated ongoing session information transfer;

FIG. 17 illustrates a wireless communications system including anembodiment of the user agent;

FIG. 18 shows a block diagram of the user agent including a digitalsignal processor (DSP) and a memory;

FIG. 19 illustrates a software environment that may be implemented by aprocessor of a user agent;

FIG. 20 illustrates an example of a system that includes a processingcomponent suitable for implementing a method for providing continuityfor sessions transitioning between networks;

FIG. 21 is an illustration of an exemplary structure for storinginformation within a network describing associated controller andcontrollee UEs;

FIG. 22 is an illustration of exemplary information stored in thenetwork such as within an HSS; and

FIG. 23 is an illustration of example indicators with reference bitvalue position.

DETAILED DESCRIPTION

The present disclosure overcomes the aforementioned drawbacks byproviding a system and method for media and/or control functionmanagement in mobile communication systems and more specifically asystem and method for implementing media transfer and/or controlfunction transfer between devices.

In one example, the method for transferring controller function from afirst user equipment (UE) to a second UE possibly belonging to the sameparty includes establishing a session for communicating media contentbetween the first UE and a third UE. The first UE is initially assignedcontroller function for the session. The method includes receiving arequest from the first UE to transfer at least a subset of controllerfunction for the session to the second UE, and determining a capabilityof the second UE to implement a controller function. When the second UEhas the capability to operate as a controller, the method includesassigning the at least a subset of controller function for the sessionto the second UE, and responding to the request to transfer at least asubset of controller function for the session to notify the first UE torelease the session.

In another example, the method for transferring controller function froma first user equipment (UE) to a second UE includes establishing asession for communicating media content between the first UE and a thirdUE. The first UE is initially assigned controller function for thesession and the first UE includes an interface. The method includesreceiving a request via the first UE interface to transfer controllerfunction for the session to the second UE, transmitting a sessioncontroller function transfer request to an application server, andreceiving a transfer response from the application server. When thetransfer response indicates that the first UE should release sessioncontroller function, the method includes releasing session controllerfunction.

In another example, a method for transferring a session forcommunicating media content between a first user equipment (UE) and athird UE includes assigning the first UE controller function for thesession, receiving a request from the first UE to transfer the sessionfor communicating media content to a second UE, and determining acapability of the second UE to receive the session for communicatingmedia content. When the second UE has the capability to receive thesession for communicating media content, the method includestransferring the session for communicating media content to the secondUE, and responding to the request to transfer the session forcommunicating media content to the second UE to notify the first UE torelease the session.

The various aspects of the disclosure are now described with referenceto the annexed drawings, wherein like numerals refer to like orcorresponding elements throughout. It should be understood, however,that the drawings and detailed description relating thereto are notintended to limit the claimed subject matter to the particular formdisclosed. Rather, the intention is to cover all modifications,equivalents, and alternatives falling within the spirit and scope of theclaimed subject matter.

As used herein, the terms “component,” “system,” and the like areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution. For example, a component may be, but is not limited to being,a process running on a processor, a processor, an object, an executable,a thread of execution, a program, and/or a computer. By way ofillustration, both an application running on a computer and the computercan be a component. One or more components may reside within a processand/or thread of execution and a component may be localized on onecomputer and/or distributed between two or more computers.

The word “exemplary” is used herein to mean serving as an example,instance, or illustration. Any aspect or design described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs.

Furthermore, the disclosed subject matter may be implemented as asystem, method, apparatus, or article of manufacture using standardprogramming and/or engineering techniques to produce software, firmware,hardware, or any combination thereof to control a computer or processorbased device to implement aspects detailed herein. The term “article ofmanufacture” (or alternatively, “computer program product”) as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (for example, hard disk, floppy disk, magnetic strips, and thelike), optical disks (for example, compact disk (CD), digital versatiledisk (DVD), and the like), smart cards, and flash memory devices (forexample, card, stick, and the like). Additionally, it should beappreciated that a carrier wave can be employed to carrycomputer-readable electronic data such as those used in transmitting andreceiving electronic mail or in accessing a network such as the Internetor a local area network (LAN). Of course, those skilled in the art willrecognize many modifications may be made to this configuration withoutdeparting from the scope or spirit of the claimed subject matter.

The present system provides media and/or control function management forimplementing media transfer or control function transfer between devicesassociated with a communications network. In one implementation, thesystem performs inter UE transfer (IUT) per 3GPP TS 23.237 fortransferring one or more media components of a session or some or allmedia flows and/or controller function (IUT controller) from one or morecontroller SIP UA's or UEs to one or more controllee SIP UA's or UEs.The system may be implemented in various communication networks whereinUEs are configured to be assigned a single shared identification (e.g.Tel URI, SIP URI, MSISDN, C-MSISDN, GRUU (Globally Routable User AgentURI), etc.), or have identification information that overlaps with otherUEs associated with the network. Within the network, each UE mayinitiate various communication sessions, each session involving thecommunication of data that may include multiple media types such as butnot limited to data for applications (media type application), voice,text, video (including various encoding schemes) and audio.

In one configuration, the system is implemented via a network thatsupports SIP and has various administrator or controller SIP UAs or UEsin addition to non-controller or controllee SIP UA's or UEs. Thecontroller function may be moved from a first controller UE to anotherUE depending upon but not limited to network rules, operator policies,user preferences, or other system requirements. In some cases, the UEsthat have controller or controllee function may be provided via anetwork wherein the controllee UEs are configured in a similar manner asthe controller UEs having similar functional capabilities and systemdesigns. When a UE among UEs is first registered with a network, thefirst UE supporting controller functionality registered with thewireless server may be automatically designated as the administrator orcontroller UE. In some cases, when a network receives an initialtransfer request for collaborative sessions sent by a UE supporting thecontroller functionality, the UE may be automatically designated as theadministrator or controller UE. However, other algorithms may beemployed to determine the preliminary controller UE amongst a collectionof UEs. After connecting to the network, a user may optionally changethe controller designation from the first registered UE to one of theother registered UEs under control by the user or by other associatedusers.

Using the present system a network serving a user with multiple UEs,each sharing a common identification, may receive an invitation toparticipate in a session that includes various media types. Afterreceiving the invitation, the network transfers, forwards, or sends thesession invitation (e.g. SIP INVITE, or SIP Re-INVITE) to the UE of theuser in accordance with the Media types described in the invitation,preferred UE specified by the user, or other information available tothe controller UE or network. If the user is already involved in asession using various media types and an offer (e.g. session descriptionprotocol (SDP OFFER) is received for the same session that adds,deletes, or modifies one or more media types, a controller UE fortransferring the new media type and session control function to adifferent UE may be identified.

In one implementation, when the UE (e.g., an ICS UE) receives a SIPINVITE request containing SDP for establishing a session using an IPbearer, the ICS UE establishes the session in accordance with 3GPP TS24.229, but with the following clarifications. First, if the SIP INVITErequest contains a Target-Dialog header containing dialog parametersthat correspond to an existing dialog (or a dialog in the process ofbeing established) between the ICS UE and Service Consistency andContinuity application server (SCC AS) the ICS UE treats the SIP INVITErequest as another dialog that is part of the same session as the dialogidentified by the dialog parameters contained in the Target-Dialogheader. Second, if the SIP INVITE request does not contain aTarget-Dialog header but there is an existing dialog (or a dialog in theprocess of being established) between the ICS UE and SCC AS, the SCC AScan check whether the dialog parameters for this request correspond tothe dialog parameters received in a Target-Dialog header received on anexisting dialog (or a dialog in the process of being established)between the ICS UE and SCC AS and if so then the ICS UE can treat theSIP INVITE request as another dialog that is part of the same session asthe dialog upon which the Target-Dialog header was received. This secondclarification may cover the possibility that requests arrive out of theorder in which they were sent.

A controller UE configured to implement IUT in accordance with thepresent system may be configured to do one or more than one of thefollowings: to add one or more media flows to a session by creating anew access leg on a different UE, to add one or more media flows to asession on an existing access leg on a different UE, to remove one ormore media flows from a session on an access leg on a different UE, toprovide MMTeI Service control with media on a different UE (see, forexample, 3GPP TS 22.173), and to provide an update of mediacharacteristics on different UEs. Accordingly, each controller UE may beconfigured to establish and/or release collaborative sessions thatprovide one or more sessions anchored with a particular network entityor node such as a SCC AS. While maintaining an on-going collaborativesession, each controller UE may transfer media flows of thecollaborative session to a target UE. Furthermore, each controller UEmay be configured to transfer all or some of the available one or moremedia flows to a target UE with or without establishing a collaborativesession. If transferring all media flows to a target UE, the existingsession on the controller UE may be released.

In one example system implementation, to implement inter-UE transfer(IUT), the SCC AS uses the ISC reference point towards the S-CSCF forexecution of the Inter-UE Transfer. For example, for enablement andexecution of IUT, the SCC AS may first analyze the information requiredfor Inter-UE Transfer as described below and decide which accessnetworks should be executed based on operator policy and userpreferences. The SCC AS may then reject the Inter-UE Transfer request ifit is not aligned with the operator policy. The SCC AS may retrieve fromthe home subscriber server (HSS) after registration the C MSISDN boundto the IMS Private User Identity stored in the user profile in the HSS.,and retrieve from the HSS after a third party registration thecontroller functionality for Inter-UE Transfer bound to the IMS PrivateUser Identity stored in the user profile in the HSS. The SCC AS may alsodetermine whether a UE is allowed and capable of controllerfunctionality for Inter-UE Transfer, correlate the Inter-UE Transferrequest with the anchored session, using information provided in theincoming SIP INVITE or incoming Inter-UE Transfer request, and executethe IMS Inter-UE Transfer between different UEs belonging to the sameIMS subscription connected via the same or different access networks.The SCC AS may also provide IUT Transfer specific charging data,provides a controller UE with information of transferable UEs, anddecide, based on analysis of the various service continuity relatedinput factors, whether to update provisioned operator policy forInter-UE Transfer. The SCC AS may also generate and update operatorpolicy for Inter-UE Transfer by sending operator policy to the UE viaOMA DM including the priority between the operator policy and userpreferences that could be used also to initiate Inter-UE Transferprocedure for ongoing sessions, and determine whether to send acontroller UE a received incoming session invitation from remote partyso that the terminating controller UE can initiate Inter-UE Transfer.

Generally, the SCC AS provides functionality to combine and/or splitmedia flows over one or more Access Networks as needed for SessionTransfers, session termination, or upon request by the UE to add mediaflows over an additional Access Network during the setup of a session,or upon request by the UE to add and/or delete media flows over one ormore Access Networks to existing sessions.

When handling media flows of an IMS session, the SCC AS may take intoaccount the services associated with the session.

In order to route SIP METHODs (such as SIP INVITE) over a particularaccess leg it is necessary to identify the particular registration flowthat corresponds to that access leg.

Draft-ietf-sip-outbound describes how a SIP UA or UE can register overmultiple registration flows by which requests can reach the UA or UE. Asis supported in 3GPP IMS the UE uses the mechanism defined inDraft-ietf-sip-outbound in order to register using different flows overdifferent access networks. Each flow over the different access networksmay, as defined in Draft-ietf-sip-outbound, contain a different “reg-id”contact header parameter in the Contact header of the SIP REGISTERrequest. When registering the UE includes a P-Access-Network-Info headerin the SIP REGISTER request as described in 3GPP TS 24.229: Examplesyntax of extended P-Access-Network-Info header field per 3GPP TS 24.229is shown in Table 1.

TABLE 1 P-Access-Network-Info = “P-Access-Network-Info” HCOLONaccess-net-spec *(COMMA access-net-spec) access-net-spec = (access-type/ access-class) *(SEMI access- info) access-type = “IEEE-802.11” /“IEEE-802.11a” / “IEEE-802.11b” / “IEEE-802.11g” / “IEEE-802.11n” /“3GPP-GERAN” / “3GPP-UTRAN-FDD” / “3GPP-UTRAN-TDD” / “3GPP-E-UTRAN- FDD”/ “3GPP-E-UTRAN-TDD” / “ADSL” / “ADSL2” / “ADSL2+” / “RADSL” / “SDSL” /“HDSL” / “HDSL2” / “G.SHDSL” / “VDSL” / “IDSL” / “3GPP2-1X” / “3GPP2-1X-HRPD” / “3GPP2-UMB” / “DOCSIS” / “IEEE-802.3”/ “IEEE-802.3a” /“IEEE-802.3e” / “IEEE-802.3i”/ “IEEE-802.3j” / “IEEE-802.3u” /“IEEE-802.3ab”/ “IEEE-802.3ae”/“IEEE-802.3ak”/IEEE-802.3aq”/ “IEEE-802.3an” / “IEEE-802.3y”/ “IEEE-802.3z”/ “IEEE- 802.3y”/ token . ..access-class = “3GPP-GERAN” / “3GPP-UTRAN” / “3GPP-E-UTRAN” /“3GPP-WLAN” / “3GPP-GAN” / “3GPP-HSPA” / token np = “network-provided”access-info = cgi-3gpp / utran-cell-id-3gpp / dsl-location /i-wlan-node-id / ci-3gpp2 / eth-location / np/ extension-access-infoextension-access-info = gen-value cgi-3gpp = “cgi-3gpp” EQUAL (token /quoted-string) utran-cell-id-3gpp = “utran-cell-id-3gpp” EQUAL (token /quoted- string) i-wlan-node-id = “i-wlan-node-id” EQUAL (token /quoted-string) dsl-location = “dsl-location” EQUAL (token /quoted-string) eth-location = “eth-location” EQUAL (token /quoted-string) ci-3gpp2 = “ci-3gpp2” EQUAL (token / quoted-string)

As can be seen from the syntax of the P-Access-Network-Info, theaccess-type indicates the access network technology used by the networkover which the SIP REGISTER request is routed. However, whilst the“reg-id” parameter uniquely identifies the registration flow, there isno current mechanism that enables the network to direct that a SIPMETHOD such as SIP INVITE be directed over a particular registrationflow. To enable this, it is possible to define and include in theContact header of the SIP REGISTER request a media feature tag thatidentifies the registration flow (the “reg-id” parameter is not a mediafeature tag). Below are examples of two possible embodiments for such amedia feature tag. Those skilled in the art will appreciate that anyconstruct of appropriate alphanumeric characters can be used to conveythe same meaning from the SIP UA /UE.

In the first example shown in Table 2, the feature tag g.3gpp.icsflow isdefined which allows a string to be included in the media feature tagidentifying the flow. This string could contain the same identifiervalue as in the “reg-id” parameter (e.g., g.3gpp.icsflow=[regid]) or itcould contain some other string, however, in one implementation thestring must be different for each registration flow. The UE could allowthe user to define human understandable labels for the string used inthe media feature tag since the user may need to use these labels toindicate to which access leg they wish to transfer a media type to whenperforming a media transfer (e.g “internet”, “cableTv”, “cellular”,“WLAN”).

TABLE 2 Media feature-tag name: g.3gpp.icsflow ASN.1 Identifier:1.3.6.1.8.2.a Summary of the media feature indicated by this tag: Thisfeature-tag when used in a SIP REGISTER request indicates a particularregistration flow that the device is using register over. Valuesappropriate for use with this feature-tag: string with an equalityrelationship. Examples “Internet”, “cableTv”, “cellular”, “WLAN” Thefeature-tag is intended primarily for use in the following applications,protocols, services, or negotiation mechanisms: This feature-tag is mostuseful in a communications application, for describing the capabilitiesof a device, such as a phone or PDA. Examples of typical use: Indicatingthe registration flow that the device is using.

In another example shown in Table 3, the existing g.3gpp.ics mediafeature tag is enhanced to also indicate whether the registration isdirectly from the mobile phone or from a network node also indicatewhich registration flow is being used.

TABLE 3 Media feature-tag name: g.3gpp.ics ASN.1 Identifier:1.3.6.1.8.2.x Summary of the media feature indicated by this tag: Thisfeature-tag when used in a SIP REGISTER request indicates that thefunction is ICS capability and may operate in ICS mode and indicates aparticular registration flow that the device is using register over.This feature-tag when used is a none SIP REGISTER method indicates thatthe function wants to invoke ICS functionality. Values appropriate foruse with this feature-tag: string with an equality relationship Someexamples “Principal[#]” When used in a SIP REGISTER request indicatesthat the function that is ICS capable is a mobile phone. When used inanother SIP method indicates that the function wants to invoke ICSfunctionality. [#] is a numerical digit indicating the particularregistration flow that the device is using register over and equates tothe SIP Outbound RegID. “server” Indicates that the function that is ICScapable is a network node. The feature-tag is intended primarily for usein the following applications, protocols, services, or negotiationmechanisms: This feature-tag is most useful in a communicationsapplication, for describing the capabilities of a device, such as aphone or PDA. Examples of typical use: Indicating that a mobile phone(principal) can support or wants to use ICS or that a network node(server) wants to invoke ICS functionality and Indicating theregistration flow that the device is using

The UE, when registering, includes the P-Access-Network-Info headercontaining the identification of the Access Technology used on thataccess leg in the the SIP REGISTER request along with a media featuretag containing a unique identifier for the flow as described above inthe Contact header of the SIP REGISTER request.

The SCC AS or another network node can obtain the media feature tag bysubscribing to the registration event package as per RFC 3860 or theenhanced third party registration procedures (e.g., Incoming SIPREGISTER request included in the body of the third party SIP REGISTERRequest). The P-Access-Network-Info header can also be obtained by theSCC AS from the third party SIP REGISTER Request.

The SCC AS may also obtain registration state information that it needsto implement IMS Centralized Services (ICS) specific requirements fromany received third-party REGISTER request (e.g. including informationcontained in the body of the third-party REGISTER request) as specifiedin 3GPP TS 24.229, any received reg event package as specified in 3GPPTS 24.229, or the Sh interface as specified in 3GPP TS 29.328 and 3GPPTS 29.329, for example. Using these mechanisms the SCC AS can obtain theaccess-type and, if present, access-class values from theP-Access-Network-Info header and the value of the g.3gpp.icsflow mediafeature tag and associate the access-type and, if present, access-classvalues with the value of the g.3gpp.icsflow media feature tag in orderthat a request can be routed over a specific flow that corresponds to aspecific IP-CAN.

The SCC AS, or another network node, stores the access-type and/oraccess class information (possibly including the associated locationinformation) obtained from the P-Access-Network-Info header inassociation with the access leg/flow identifier obtained from the mediafeature tag. Note that the P-CSCF can also include additional accesstypes or access class values in the P-Access-Network-Info headercontaining the access class and access type as verified by the networkand indicated as such by the inclusion of the “np” (network provided)parameter. Based upon availability and the policy of the operator, theaccess type and/or the access class from either the UE providedP-Access-Network-Info header or the network providedP-Access-Network-Info header or both may be stored in association withthe access leg/flow identifier obtained from the media feature tag.

When the SCC AS (or another network node) based upon an operator policyor user preference or user configuration determines that a requestcontaining certain offered media types is to be routed over a certainaccess leg, the SCC AS (or another network node) obtains the accessleg/flow identifier previously obtained from the media feature tag thatis stored in association with access type and/or the access class fromthe P-Access-Network-Info header. Then the SCC AS (or another networknode) includes in the request an Accept-Contact header containing themedia feature tag (e.g g.3gpp.icsflow) with the value set to the accessleg/flow identifier that was associated with the access type and/or theaccess class for the access leg that the request is to be routed over.The parameters “require” and “explicit” may optionally also be includedin the Accept-Contact header associated with the media feature tagcontaining the access leg/flow identifier. As a result, the request isrouted to the UE using the desired access leg using the mechanismdescribed in RFC 3841 and correspondingly if the request is accepted themedia to also be established using that access leg.

In some implementations, the network operator's policy is provisioned inthe network by the operator, and can be communicated to the UE duringinitial provisioning or via OMA Device Management, for example. Theoperator policy may be communicated to the UE, via OMA DeviceManagement, whenever the policy is updated by the operator.

The operator policy may indicate, for each supported type of media orgroup of media, a list of access networks that are restricted fororiginating sessions and session transfer, a list of preferred accessnetworks (in order of priority) to be used by the UE with SCcapabilities for originating sessions and session transfer, when thoseaccess networks become available and session transfer is possible, andwhether the UE with SC capabilities “shall”/“should”/“may” starttransferring media flow(s) to target access networks with higherpriorities than the current access network, when the target accessnetworks become available and session transfer is possible. Byindicating “shall”, the operator mandates the UE to start sessiontransfer according to the home operator's list of preferred accessnetworks as soon as possible. By indicating “should”, the operatorrecommends the UE to start session transfer according to the homeoperator's list of preferred access networks, if session transfer ispossible and desirable after having taken into account the LocalOperating Environment Information. By indicating “may”, the operatorleaves the UE free to decide whether or not to start session transfer inaccordance with user preferences (when configured), if session transferis possible and desirable after having taken into account the LocalOperating Environment Information. Whenever user preferences are notconfigured, the UE may take into account the home operator's list ofpreferred access networks. The operator policy may also indicate whetherto keep or drop non transferable media flow(s) in the case of partialsession transfer. Generally, the operator policy for ession transfer isconsistent with operator policy for T-ADS.

User preferences may indicate, for example, preferred access. The LocalOperating Environment Information can be implementation specific and maycomprise of such items as radio environment information, quality of IPconnection (jitter, delay and packet loss), application specificrequirements, memory considerations, power considerations, etc. The UEmay take in account operator policy, user preferences and the LocalOperating Environment Information when deciding which access to use foroutgoing sessions or before considering initiating Session Transfer.Generally, user preferences for Access Transfer are not transferred tothe network.

For IUT, the UE may indicate the following user preferences to the SCCAS via Ut interface and the SCC AS may take in account operator policyand user preferences when deciding whether the UE is allowed and able toact as a controller and for determining which access network to use forincoming sessions, which media type to transmit on certain UE andwhether to send a controller UE incoming session invitation from remoteparty: preferred UE to act as a controller UE; preferred access networktype for incoming sessions; preferred media type to be received onparticular UE of the user; and preference to receive incoming sessioninvitation from remote party on a controller UE.

Furthermore, for IUT, the UE is generally configured to support an IUTcontroller or controlee functionality. In the case of a terminating UE,the UE may be configured to become a Controller UE in order to apply IUTfor the ongoing session when a remote end sends a session invitation.

If the user wishes to direct that a media session be established for oneor more media types over a particular access leg when performing a mediatransfer the user can indicate this by selecting on their controller UEthe access leg they wish to use for the particular media type. The UEcould have previously allowed the user to define human understandablelabels for the string used in the media feature tag so that the user canuse these labels to indicate which access leg they which to transfer amedia type when performing a media transfer (e.g “Internet”, “cableTv”,“cellular”, or “WLAN”). Alternatively, the device, when registering overan access type, provides a mapping between human readable access typesthat the user can read and the access types that the device supports.Example embodiments are below but those skilled in the art willappreciate that the mapping could be more or less constrained where theidea is that a human readable alphanumeric string is mapped against anumber of possible P-Access-Network-Info header access type values.

E.gWLAN=“IEEE-802.11”/“IEEE-802.11a”/“IEEE-802.11b”/“IEEE-802.11g”/“IEEE-802.11n”

DSL=“ADSL”/“ADSL2”/“ADSL2+”/“RADSL”/“SDSL”/“HDSL”/“HDSL2”/“G.SHDSL”/“VDSL”/“IDSL”

Cellular=“3GPP-GERAN”/“3GPP-UTRAN-FDD”/“3GPP-UTRAN-TDD”/“3GPP-E-UTRAN-FDD”/“3GPP-E-UTRAN-TDD”

CableTV=“DOCSIS”

For example, if the user has a multimode capable mobile phone thatsupports both WLAN and Cellular (e.g EDGE/UMTS/LTE) accesssimultaneously, the user may wish the video media type to be receivedover the WLAN access for reasons of bandwidth efficiency, costefficiency or better picture quality while using the Cellular connectionfor voice and audio media types. To do this the UE includes in therequest used to request the media transfer (e.g a SIP REFER request) anAccept-Contact header containing the media feature tag (e.gg.3gpp.icsflow) with the value set to the access leg/flow identifier forthe access leg that the user selected the transferred media type is tobe routed over. The parameters “require” and “explicit” may optionallyalso be included in the Accept-Contact header associated with the mediafeature tag containing the access leg/flow identifier. TheAccept-Contact header along with its values could in the case of a SIPREFER request be embedded within the Refer-To header. When the SCC AS(or another network node) receives the media transfer request it thenincludes the Accept-Contact header along with its values from the mediatransfer request in the request sent to the UE the media is to betransferred to. This causes the request to be routed to the UE using thedesired access leg using the mechanism described in RFC 3841 and,correspondingly, if the request is accepted, the media to also beestablished using that access leg. Note that the UE the media is to betransferred to could, in some cases (such as the example above), be thesame UE acting as the controller UE sending the media transfer request.

FIG. 1 illustrates an example communication flow that may be implementedby the present system to transfer media and/or IUT controller functionbetween SIP UA's or UEs associated with a network. The flow allows fortransferring service control of a session containing two mediacomponents from a first controller UE (UE-1) to a second controllee UE(UE-2). Both the first and second UEs may share the same public useridentity for example by sharing the same SIP URI or Tel URI, or havingoverlapping or identical public user identities defined by an ImplicitRegistration Set (IRS). They will however have unique Private Identitiessuch as but not limited to IMS Private Identity, IMSI, MIN etc. In thisexample, UE-1 has an established multimedia session with a remote UE,whose session is anchored at an SCC AS. UE-1 initially facilitatescollaborative session control.

As shown in FIG. 1, the multimedia session includes two media components(Media-A and Media-B) and UE-1 wants to transfer the collaborativesession control and one of the media components (media-A) to UE-2 via anIUT. As illustrated, in step 101, UE-1 initiates the process oftransferring the collaborative session control and media type (media-A)to UE-2 by communicating or sending a transfer request to the SCC AS.The transfer request indicates that the collaborative session controland media type (Media-A) are to be transferred to UE-2. The transferrequest may contain SDP (possibly embedded in the Refer-To header of aSIP REFER request) containing the media type to be transferred.Alternatively, the media type may be indicated by signalling theappropriate feature tags etc. in the Transfer Request. The UE-2 may beidentified by, but not limited, to GRUU, SIP URI, Tel URI, etc. In step102 the SCC AS identifies the request, and performs a verificationprocess. The verification process may include verification that UE-1 isallowed to perform IUT, and UE-2 identification, in this embodimentUE-2's GRUU is stored in the SCC AS (valid REGISTRATION exists) andstored against that GRUU are media feature tags that match those thathave been received in the request from UE-1. If UE-2's GRUU does notexist or feature tags do not match then the request may be rejected.Alternatively, the verification process may include the SCC ASretrieving a Tel URI, SIP URI of an authorized UE. If the retrieved TelURI, SIP URI matches one UE-1 could use, then the SCC AS may identifyanother target UE that matches the retrieved Tel URI, SIP URI. The SCCAS would then ensure that the feature tags in the accept contact headerand the explicit and required parameters are set to choose analternative contact to that of the one performing the request.

If UE-1 is allowed to request transfer of the collaborative sessioncontrol and the media-A to UE-2, the SCC AS may communicate or send arequest to UE-2 indicating that the collaborative session control andMedia-A will be transferred to UE-2. For example, the SIP METHOD (e.g.,SIP INVITE) may include as the target the GRUU of UE-2 along with amedia feature tag that indicates the collaborative session control (IUTController function). The SIP METHOD may include in the Accept-Contactheader the required media feature tags with “Explicit” and “Required”.Alternatively, SDP is included that contains the media type to betransferred. In step 103 the system establishes collaborative sessioncontrol between UE-2 and the SCC AS. As this point UE-2 becomes thecontroller UE (based upon receiving the media feature tag that indicatesthe IUT controller function) for the collaborative sessions. In otherimplementations, however, UE-1 may send a transfer request including theMedia to be transferred, while keeping the collaborative session controlon the UE-1 In this case the transfer request doesn't include theindication, identifier, token, flag, or media feature tag of thecollaborative session control (IUT Controller function).

In one implementation, the collaborative session includes a logical setof one or more IP Multimedia Subsystem (IMS) sessions, possibly on twoor more UEs sharing the same IMS subscription, anchored in the SCC ASthat are presented on the remote leg as a single IMS session. The remoteleg may be the call control leg between the SCC AS and the remote partyas seen from the subscriber's perspective (for an additional example,see 3GPP TS 23.292 for the definition of Remote Leg for IMS sessionswhich use circuit switched media).

In step 104, a session carrying media-A between UE-2 and the SCC AS isestablished. At this point, the system may optionally update the remoteleg between the SCC AS and the remote party in accordance with theestablishment of the new session with UE-2. For example, the remote legmay be updated to implement a video codec adjustment or change (e.g.,because a change is required by an IPTV device, or to otherwiserenegotiate the media). After successful establishment of thecollaborative session control and transfer of media-A to UE-2, the SCCAS sends a transfer response back to UE-1 in step 105 (e.g., a SIPNOTIFY request for a final response as per RFC 3515). After receivingthe transfer response, the prior session carrying media-A on UE-1 may bereleased and the collaborative session control is released in step 106.After successful transfer of collaborative session control, UE-1 becomesa controllee UE (a UE that receives and/or transmits media flow(media-B) as part of the collaborative session, while being subordinateto the controller UE for session control) and UE-2 assumes the role ofcontroller UE. Media type (Media-A) is communicated between UE-2 and theremote party and media type (Media-B) continues to be communicatedbetween UE-1 and the remote party. If the transfer was not successfulthe SCC AS shall send a message back to UE-1 indicating failure of thetransfer. The message can include but not limited to a SIP 488 (NotAcceptable Here) response. A Warning may be included in the responseindicating the reason for the failure. The message to UE-1 indicatingfailure of the transfer may be contained in a SIP NOTIFY requestcontaining in the body a SlPfrag of the response from UE-2 (e.g., a SIP488 (Not Acceptable Here) response)).

The communication flow illustrated in FIG. 1 allows for the transfer ofmedia and collaborative session control between UEs. In addition tomedia and collaborative session control transfer, the above flow mayalso transfer the controller function between UEs after one or morecontroller UEs authorize to give the controller function to the targetUE.

In one implementation, to facilitate session transfer (e.g., for IMSservice continuity), the UE may be configured to store and apply anoperator policy (e.g,. as described above) for session transfer. The UEmay also initiate session transfer procedures based on trigger criteriaincluding the current operator policy, user preferences and the localoperating environment information, providing the necessary details forconducting a Session Transfer operation to the SCC AS. The UE may alsoprovide its capability to support controller or controlee functionalityfor IUT, and initiate IUT procedure based on the current operator policyand user preferences, providing the necessary details for conducting anIUT operation to the SCC AS.

A UE can have multiple registration contexts possibly using differentaccess networks. A UE, depending upon the IUT policy and implementationin the network or Application Server (AS), may be configured to usedifferent access networks for some or all media transmission. Forexample, a UE may use a Wireless Local Area Network (WLAN) radio or someother access network for video type media transmission that hasappropriate properties according to some predefined user preferences ornetwork/operator policy.

An indicator indicating properties or a target UE or a specific targetUE can also be capable of identifying an access technology (e.g.,supported by the same device). Requests can be routed over a particularaccess leg that uses a particular access technology using the proceduredescribed above.

In other system implementations the controller UE functionality may alsobe hosted in a physical box such as a set-top box or executable softwarehosted on a Personal Computer, Media Server, Home NodeB, or other devicethat is not physically operated by a user. In one example, a user issurrounded by media sinks or controllee UEs. The media sinks may enableinteraction with or supplement the controller UE or other mediacontroller device. For example, a TV remote may offer stop and rewind orother functions that are intercepted by the media sink or TV andforwarded to a device or UE configured to handle various functions. Insome implementations a single box may support multiple SIP UAs fordifferent external physical devices. For example a home server or settop box may implement multiple SIP UAs for other connected non SIPcapable devices such as basic TVs, legacy fixed line phones, and non SIPenabled home entertainment systems.

Referring now to FIG. 2, an exemplary communications network forimplementing the present system for performing IUT is illustrated.Network 212 is a communications network and includes various componentssuch as a base station, SCC AS, Call Session Control Function (CSCF)such as P(Proxy)-CSCF, S(Serving)-CSCF, and I(Interrogating)-CSCF,mobile switching center (MSC) server, MSC enhanced for IMS CentralizedService (ICS) and/or various data storage systems for storing devicecapability, user preferences, lists of controller UEs and controllee UEsfor IUT, session leg mapping information per device, and other rules orrestrictions used in implementing the present system. By communicatingwith network 212, UEs can become associated (e.g., REGISTERED) with thenetwork and communicate through network 212 with other associated UEs,or other devices configured to communicate via network 212. User 214 hasseveral UEs 216, 218, and 220. UEs 216, 218 and 220 share a singleidentity 230 that may be defined by a Tel URI or SIP URI, for example inIRS set A. User 222 has UEs 224 and 226 which are also connected tonetwork 212. UEs 224 and 226 also share an identity, by an IRS B, forexample.

In FIG. 2, the UEs of user 214 include several different devices. UE 216is a cell-phone having no video capacity, UE 218 is a laptop havingvoice-over-IP (VoIP) and video-conferencing capabilities, and UE 220 isa television configured to communicate with network 212, but havingminimal user-input capability. In the present example, television 220 isconnected by a hard-wired connection to proxy 221 for communicating withnetwork 212. Proxy 221 may include a home gateway, cable box, set-topbox, or other system for communicating with network 212. Proxy 221 maycommunicate with network 212 wirelessly, or via a hard-wired connection.However, those skilled in the art will appreciate that some or all ofproxy 221 may be incorporated into television 220. As each of UEs 216,218, and 220 establishes a connection with network 212, IUT-Controllerfunction may be assigned to one or more of the UEs associated with user214. The IUT-Controller function may be assigned based upon rules thatevaluate any combination of the UE's functional capabilities, userpreferences, network requirements, or other data made available via user214, network 212, or any other entity in communication network 212. Inthe present example, UE 216 (a cell phone) is initially allocated IUTcontroller function. As such, UE 216 may send a transfer request ofcertain media on ongoing sessions to any one of UEs 218 and 220. As partof the transfer process, UE 216 may also issue a request to network 212to transfer IUT controller function to any of UEs 218 and 220. In somecases, depending upon network-defined and user-defined rules, some orall of media and IUT controller function may be transferred to UEs 224and 226 belonging to user 222.

With reference to FIG. 2, user 214 may initiate a phone call usingcell-phone 216 to UE 232 belonging to user 230. Because cell-phone 216does not support video, the established session includes only voice withno video. If, however, UE 232 of user 230 supports video and user 230wishes to add video to the session user 230 may issue a request orinvitation to user 214 to add video to the session. Because cell phone216 cannot handle video, video cannot be added to the session unlessuser 214 instructs the UE 216 to redirect to a UE that can handle video.In this example, when receiving a request to add video to the ongoingsession, user 214 may instruct the UE 216 to redirect the request withvideo type to laptop 218 having video-conferencing capabilities. Toredirect the request with video to laptop 218, cell phone 216 generatesa message such as a SIP 3xx non-final response in order to redirect therequest with video type to network 212 (if a final SIP response was usedsuch as a SIP 3xx response, the whole session could be redirected).Depending upon the system implementation, when receiving the request toadd a new media type from a remote party, a network (e.g., SCC AS) mayautomatically initiate an invitation to the target UE based upon devicecapability, user preferences, or network rules, for example.Alternatively, a user interface provided by cell phone 218 may allowuser 214 to instruct cell phone 218 to redirect the message to laptop218. After network 212 (e.g., SCC AS) receives the request to redirectthe request network 212 (e.g., SCC AS) verifies that laptop 218 cansupport the video type media. This consists of the SCC AS 212 looking atthe media feature tags that were passed to the SCC AS 212 as part of thelaptop 218 SIP REGISTRATION and stored in the SCC AS 212 againstREGISTRATION laptop 218 GRUU Media Feature tags.

SCC AS 212 verifies that cell phone 216 has the capability to requestthe redirection and is authorized to do such a request. If theserequirements are met, SCC AS 212 may check whether the feature tagcontained in the SIP METHOD (e.g., SIP INVITE) from the controller isstored against the SIP Contact that the media is being redirect to. Ifthe media feature tag is present, the SCC AS redirects the request tolaptop 218 by sending an invitation request (e.g., a SIP INVITE) withSDP containing the media type. The SCC AS also sets the “Explicit” and“Required” per RFC 3841 to ensure that the correct target is chosen inthe S-CSCF. Upon successful redirection and collaborative sessionestablishment, cell phone 216 may also request a transfer of IUTcontroller function to laptop 218.

In the present example, IUT controller functionality is transferred tothe laptop 218. As such, laptop 218 has the option of again having thevideo-conference session to other UEs accessible to user 214. Forexample, to facilitate viewing of the ongoing video conference by alarger collection of people, user 214 may wish to duplicate some or allof media on the video conference to a television 220 while keeping thevideo conference on the laptop 218 that is configured to communicate vianetwork 212. In this example television 220 does not include amicrophone. As such, user 214, using laptop 218 (which has IUTcontroller status), instructs network 212 to duplicate only the videoportion of the ongoing videoconference session to television 220. In oneimplementation, where the SCC AS releases the media type from thetransferred leg after the transfer, it is necessary to signal thatduplication is requested. The duplication may be signaled using a newmedia feature tag, SDP variable, parameter, and/or SIP header. Inanother implementation, where the transferring UE releases the mediatype from the transferred leg after the transfer, no signaling ofduplication being requested is required. Upon authorizing theduplication, SCC AS 212 sends a message such as a session invitation(SIP INVITE) with video media type to television 220 to facilitateviewing. The voice portion of the session, however, stays with laptop218 so that user 214 can continue communicating with user 230. In thisexample, television 220 also has no user interface for receiving auser-input for initiating additional media transfers. Accordingly, IUTcontroller status stays with laptop 218 so that user 214 may transferthe video portion of the videoconference from television 220 to anotherdevice. If the IUT controller status were to be transferred to legacytelevision 220, there may be no mechanism by which to transfer thesession to another device because legacy television 220 cannot providethe appropriate user interface for initiating such a transfer—the videoportion of the session would become stuck with the legacy television220.

Depending upon the system implementation, various policies orrestrictions may be applied to the number and combination of UEs thatmay be established for each user. For example, a network may implementrestrictions that state only one IUT controller capable UE can become anIUT controller, or multiple IUT controller capable UEs can become IUTcontrollers for any collaborative sessions, multiple IUT controllercapable UEs can become IUT controllers with multiple UEs for allcollaborative sessions but with only one IUT controller UE per the samecollaborative session. Furthermore, a preferred bearer (circuit switchedor packet switched, for example) may be specified by network rules, userpreferences, or a combination thereof. For example, the preferred bearersetting may depend on media type and device capability e.g. circuitswitched for speech media type sessions, and packet switched for videotype sessions.

The network (e.g., SCC AS) may also use the following indications forcharging purposes: an indication of which UE is an IUT controller, UEidentity performing an IUT controller function, subscription setindication for IUT which indicates a set of UEs belong to the samesubscription, and a bearer indication (there may be different chargesdepending upon the bearer being used).

In the present system, each UE may be configured to communicate with thenetwork (e.g., via the SCC AS or another component of the communicationsnetwork) to instruct the network, in this instance the SCC AS, as towhether the UE has the capability to support IUT controllerfunctionality. In one implementation, the UE transmits its capabilitiesto the SCC AS such as using a SIP message including either a SIP METHODsuch as SIP REGISTER, SIP PUBLISH, SIP SUBSCRIBE, SIP NOTIFY, SIPINVITE, SIP Re-INVITE, SIP UPDATE, SIP OPTIONS and SIP REFER or a SIPResponse or eXtensible Markup Language—Configuration Access Protocol(XCAP) or Web Services based, e.g. using SOAP, or HTTP. One way for a UEto transmit its capabilities to the SCC AS is to use a media feature tage.g. g.3gpp.iut in a Contact header. For example, SIP METHODs such asSIP REGISTER, SIP SUBSCRIBE, SIP NOTIFY, SIP INVITE, SIP Re-INVITE, SIPUPDATE, SIP OPTIONS, SIP PUBLISH, and SIP REFER that include a Contactheader may be configured to include an IUT controller media feature tagto indicate a particular UE's support for IUT controller functionality.Alternatively, SIP responses, such as SIP 200 OK, can also include aContact header that may be configured to indicate a UE's controllercapabilities.

When implemented using Contact headers, the IUT controller feature tagmay include, for example, three possible values (only exemplary valuesare described as the system may use other values having various namesand attributes). First, a value “Active” may indicate that the UE withthe contact address associated with the IUT controller feature tag iscurrently acting as the IUT controller for the session. Second, a value“Inactive” may indicate that the UE with the contact address associatedwith the IUT controller feature tag is currently acting as an IUTcontrollee (i.e., not the Active IUT Controller) for the session but iscapable of being assigned the IUT controller role. Third, a value“Passive” may indicate that the UE with the contact address associatedwith the IUT controller feature tag is currently acting as an IUTcontrollee for the session and is incapable or unwilling to accept theIUT controller role. Passive could also mean that device can act as acontrollee but does not have controller functionality.

In some implementations, the IUT controller indication may include twopossible values such as (Active, Inactive) or (Active, Passive) on anyparticular UE. Example value definitions may include:g.3gpp.iutcontroller=“active” or g.3gpp.iutcontroller=“passive”. In somecases, the IUT controller value is prefixed with a version indicator.For example, the IUT controller value may be “activeX” where X can be avalue from 0 or 1 to Y that indicates the version of IUT supported bythe UE. Another example is g.3gpp.iut=[capability] whereby capabilityindicates the capability of the IUT device such as being a “controller”or a “controllee”. Controller could be extended to be “activecontroller”or “passcontroller”. Active controller means that the SIP UA/UE isperforming controller activities for the session and passcontrollermeans that the SIP UA/UE has controller capabilities but is not actingas a controller. An example definition of the feature tag is providedbelow in Table 4, however those skilled in the art will appreciate thatany construct of appropriate alphanumeric characters can be used toconvey the same meaning from the SIP UA/UE.

TABLE 4 Media feature-tag name: g.3gpp.iut ASN.1 Identifier:1.3.6.1.8.2.y Summary of the media feature indicated by this tag: Thisfeature-tag indicates that the device has IUT capabilities. Valuesappropriate for use with this feature-tag:active, controller,controllee. The feature-tag is intended primarily for use in thefollowing applications, protocols, services, or negotiation mechanisms:This feature-tag is most useful in a communications application, fordescribing the capabilities of a device, such as a phone or PDA.Examples of typical use: Indicating that a mobile phone supports IUTfunctionality.

In other implementations, a UE supporting IUT controller function can beconfigured by a user to activate or deactivate the IUT controllersetting based on a user preference using SIP, XCAP, etc. The activationor deactivation setting of an IUT controller UE or Controllee UE may beplaced into the XML MIME body of a SIP or XCAP message, for example. Ifan IUT controller setting is activated on a UE then the UE acts as anIUT controller UE. If an IUT controller setting is deactivated on a UEthen the UE acts as an IUT controllee UE. The following is an example ofsetting IUT controller functionality for a particular UE in XML:

<?xml version=“1.0” encoding=“UTF-8”?> <iutcont-settingsxmlns=“urn:3gpp:params:xml:ns:ims:iutcont-settings”xmlns:xsi=http://www.w3.org/2001/XMLSchema-instancexsi:schemaLocation=“urn:3gpp:params:xml:ns:ims:iutcont-settings”><entity id=“do39s8zksn2d98x”> <iutcont-settings><interuetransfer-controller active=“true” /> </iutcont-settings>

In addition to notifying the network of whether a particular UE has thecapability and is preferred to act as a controller UE, the presentsystem allows UEs that support multiple bearers to be configured toindicate a preferred bearer by a user to the network, which stores suchinformation such as UE capabilities and user preferences. Depending uponthe UE, the UE may have the capability to communicate with a networkusing circuit switched, packet switched communication protocols or both,for example. For UEs that support multiple bearers, the preferred bearermay be specified through user preferences via SIP, XCAP, or otherencoding schemes. In one implementation, a preferred bearer is specifiedin accordance with a particular media type and/or device capability. Forexample, a particular bearer may be specified for particular media typeson devices having particular capabilities. Alternatively, a generalbearer preference may be specified for all UEs, regardless of media typeand/or device capability. The bearer preferences may be specified in theXML MIME body of an SIP or XCAP message, for example. The followingshows exemplary coding in XML:

<?xml version=“1.0” encoding=“UTF-8”?> <iutcont-settingsxmlns=“urn:3gpp:params:xml:ns:ims:iutcont- settings” xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:schemaLocation=“urn:3gpp:params:xml:ns:ims:bearer-  settings ”><entity id=“do39s8zksn2d98x”> <bearer-settings><preferred-bearer>PS</preferred-bearer> </bear-settings>

Upon receiving a message indicating a UE's capability and, optionally,user preferences relating to a preferred bearer for the UE, one or morenetwork components such as a Call Session Control Function like P-CSCF,S-CSCF, I-CSCF, mobile switching center (MSC) server, MSC enhanced forICS or the SCC AS may verify that the UE is allowed and able to act as acontroller if the message includes that IUT controller function issupported on the UE and a preference to use the UE as a controller. Inone embodiment, the SCC AS may also verify that the UE supports and hasregistered for a particular bearer if the received message contains thesupported bearer type and/or a preference to use a particular bearertype.

During verification, the SCC AS determines which UEs are to be acontroller, for example by inspecting the IUT controller media featuretag in the Contact header of a SIP REGISTER request. In oneimplementation, the SCC AS obtains the media feature tags using thesubscription registration event package or the enhanced third partyregistration procedures (Incoming SIP REGISTER request included in thebody of the third party SIP REGISTER Request). The SCC AS may alsodetermine a bearer that can be used for the registering UE. If apreferred/supported bearer value in the policy of the network isdifferent from that of the received message, the preferred/supportedbearer value defined by the network policy may take precedence. Requestscan be routed over a particular access leg or preferred bearer that usesa particular access technology using the procedure described above.

In order to verify that the UE meets certain requirements for theassignment of controller function and/or a particular bearer assignment,the network maintains a database storing Public User Identities of auser e.g. Tel URI, SIP URI etc , Private User Identities of a user e.g.IMS Private User Identity, IMSI etc, which UEs (e.g., instance ID, IMEI,MIN, or GRUU) belong to the same subscription set, which UEs belong tothe same IUT, which UEs are capable of IUT controller function, deviceidentity such as (instance ID, IMEI, MIN, Globally Routable UA URI(GRUU), device nickname mapping to each device, session leg mappinginformation connected with each device, supported and preferred beareror radio access technology (RAT) on each UE, addresses identifying eachUA per RAT for UEs or intermediaries that support multiple PS accesstechnologies or multiple subscriptions or peer-to-peer (P2P) servicesand have at least one UA per RAT or subscription or P2P service,authorization rules to permit another UE to obtain the controllerfunction, and other information describing or associated with the UE.This database may be stored in the HSS and accessed by the SCC AS usingSh interface or the information maybe received from S-CSCF as a resultof a registration. The database could be stored in other entities withinthe network. Maybe internal to the SCC AS or combination there of. Inone implementation, to perform registration activities, the network maycheck the IRS for the UE in the database to see that the UE requestingregistration has the same IRS set as that of an authorized UE. If theregistering UE uses same IRS set as that of an authorized UE stored inthe database, the IRS set may indicate particular capabilities describedby the IMS private ID, and whether the UE may be a controller orcontrollee. Furthermore, the IRS set may indicate whether the UE canonly be controlled, and whether the UE can subscribe in and out of theservice.

During operation of the present system, a network node distributes alist of URIs or identities of IUT UEs (i.e. a set of URIs or identitiesof UEs which can request IUT transfer or be transferred, or a set ofURIs of controller and controllee UEs belonging to the same IUT set) tothe controller UEs or a set of IUT UEs allowing the identification ofwhich UEs are controller or controllee, which UEs support IUT controllerfunction and to which UE an IUT controller function can be transferred.The list of URIs or identities of IUT UEs may include information suchas device nickname, supported media types per URI or identity of eachIUT UEs.

When a UE registers with the network the UE will include the feature tagdescribed above. The GRUU of the UE is stored as part of theregistration process. This GRUU is then communicated as a URI to allpotential controller UEs. The information sent can also includequalifications if the UE identified by the GRUU is an IUT controller,controller (passive role) and controllee, controllee capable or legacycapable. Media types supported, registered RATs, etc., may also becommunicated to assist the UE if the UE acts as a controller. If thedevice performs a re-registration and the media tags (including, forexample, registered RATs) have changed then this may cause a refresh ofthe information that is sent to the IUT controller capable UEs.

As illustrated in FIG. 3, UE Registers with the IMS network in step 301,which causes registration with SCC AS. The SCC AS needs to determine ifthe device that has registered is part of the IUT set. This maybedetermined by the SCC AS being aware that there is already 1 to many UEsthat are IUT capable in the same IRS, if the SCC AS can make thisdetermination at Y in step 302 then the SCC AS will communicate with theOMA DM server in step 303. The SCC AS can include necessary identitiesto the OMA DM server so that it can communicate the information to thenecessary devices, or other devices that need the information in step304. The may include a list of Instance IDs, equipment identifies. Thesewould have been obtained in the registration process. In some cases, ifthe ICS UE has an IMEI, prior to performing registration, the ICS UEgenerates an instance ID based on its IMEI as defined in 3GPP TS 23.003.

In another implementation there may be some form of IUT group identifier(see the example in Table 5) sent when a UE registers, this identifieridentifies the IUT group allowing subscribers from different IRSs to bein the same IUT group. In that case, the SCC AS would then check when aUE registers if the UE is part of the IUT set. A possible embodiment onthe IUT group identifier could be a new media feature tag or anextension of the one defined earlier. E.g. .3.gpp.iutgroup=[variable].

TABLE 5 Media feature-tag name: g.3gpp.iutgroup ASN.1 Identifier:1.3.6.1.8.2.y Summary of the media feature indicated by this tag: Thisfeature-tag indicates that what IUT group the device belongs to. Valuesappropriate for use with this feature-tag: group identifier typenumerate. The feature-tag is intended primarily for use in the followingapplications, protocols, services, or negotiation mechanisms: Thisfeature-tag is most useful in a communications application, fordescribing the capabilities of a device, such as a phone or PDA.Examples of typical use: Indicating the group(s) that the IUT devicebelongs to.

In one implementation, when distributing the list of URIs or identitiesof IUT UEs the address of the serving SCC AS may also be included andprovided via Open Mobile Alliance Device Management (OMA DM), ClientProvisioning or other device management and provisioning protocols. Todistribute the list of URIs or identities of IUT UEs, the network mayuse over the air transport mechanisms such as, but not limited toUnstructured Supplementary Service Data (USSD), Short Message Service(SMS), Multimedia Broadcast Multicast Service (MBMS), CellBroadcast, IPpipes running over GPRS in GERAN, UTRAN, LTE, WLAN, WiMax, or CDMA2000.The identifying URIs may be TEL URIs (E.164 numbers), SIP URIscontaining a Public User Identity or a Globally Routable User Agent URI(GRUU). The list may also be provisioned in a removal memory module thatcould be but not limited to: USIM, SIM, R-UIM, UICC, or Compact flash.Alternatively, other configuration management mechanisms could be usedsuch as the SIP CONFIG FRAMEWORK as described indraft-ietf-sipping-config-framework.

The list of URIs or identities of IUT UEs may be updated periodically ornot periodically by re-broadcasting, sending, or communicating the list,broadcasting updates only as the list is changed and updated, or by eachcontroller UE requesting an updated list. Alternatively, the list may beupdated by communicating updated information directly to each UE, forexample via a user interface, or by providing the UEs with physicalmedia containing the updated list. The list of URIs on the UE is updatedwhen the other UEs belonging to the same IUT group which may use the IRSset, register or deregister. Updating the list of URIs or identities ofIUT UEs may be important as UEs may be constantly added (or registered)or removed (or de-registered) to/from the serving network entities suchas HSS, S-CSCF, SCC AS in the serving network such as S-CSCF, HSS, orSCC AS. Updates may include the deletion, addition, or modification ofentries as described above. The network node such as the SCC AS, DMServer provides the list of URIs or identities of IUT UEs.

FIG. 4 illustrates an exemplary allowed IUT List Management Object foridentifying one or more IUT UEs. MO 440 includes a root node 442 thatmay act as a placeholder for zero or one accounts for a fixed node.AllowedIUTEntries interior node 444 may be used to provide a referenceto a list of subscription set IDs and may include a run time node 446 asa placeholder for one or more subscription set IDs. Run time node 446may include a reference to a list of URIs or identities for one or moreIUT UEs, device nicknames and/or media tokens. Additional run time node450 may be used as a placeholder for IUT_URI (i.e., URI or identity ofeach IUT UE), device nickname and media token datasets. Run time node450 may include leafs 452, 454, and 456 for storing IUT_URIs, devicenicknames, media tokens, or other data.

If there is only one subscription set for the UE, then the illustratednode may not exist in the MO. The illustrated node may be added forscalability purposes, for example, in case a user has multiplesubscription sets for IUT UEs. There may be various nodes includedwithin the MO (they are not all mandatory) such as, but not limited to,either IUT URI (i.e. URIs or identities of IUT UEs) nodes or DeviceNickname nodes corresponding to the IUT URI or both in the MO. A MediaToken node for the Device may also be included in the MO. FIGS. 5 a and5 b illustrates details of the parameters and DDF of the allowed IUTList MO shown in FIG. 4. Elementary Files may also be used to distributea list of URIs or identities of IUT UEs. Exemplary Elementary Files (EF)are provided below and can be used to provide for allowed IUT Lists(EFAIUTL), IUT Device Nickname (EFIUTDN), IUT Media Token (EFIUMT), andIUT controller Indication (EFIUTCONTI) definitions. When using an EF inthis manner, the EF may be included on any of a USIM, SIM, R-UIM, UICC,or Compact flash, for example.

A first exemplary EF includes the EF_(AIUTL) (Allowed IUT Lists) and isillustrated in Table 6. The EF may contain the coding for IUT URIs ofUE, i.e., URIs or identities of IUT UEs, (or Device Nickname) belongingto the allowed IUT lists. Furthermore, for each IUT URI (or DeviceNickname) in the list, a link to the corresponding Device Nickname (orIUT URI), Media Token and IUT Controller indication may be provided. TheAllowed IUT Lists TLV object may include one or several IUT List TLV,where each IUT List TLV is associated with one or more than one amongTEL URI, SIP URI, GRUU, Instance ID, IMEI, etc. Exemplary Allowed IUTLists information is illustrated below in Table 7

TABLE 6 Identifier: ‘xxxx’ Structure: transparent Optional SFI: ‘xx’File size: X Update activity: low Access Conditions: READ ALWAYS UPDATEADM DEACTIVATE ADM ACTIVATE ADM Bytes Description M/O Length 1 Number ifIUT Lists M 1 byte 2 to X Allowed IUT Lists TLV object M X − 1 bytes

TABLE 7 Description Value M/O Length (bytes) 1^(st) IUT List Tag ‘80’ M1 Length K M Note 1^(st) IUT List — M K . . . . . . . . . . . . n^(th)IUT List Tag ‘80’ M 1 Length L M Note n^(th) IUT List — M L Note: Thelength is coded according to ISO/IEC 8825

In Table 7, the contents of the IUT List Tag ‘80’ may include theallowed IUT list per IUT Subscription set that is applicable to the oneor more than one among TEL URI, SIP URI, GRUU, Instance ID, IMEI, etcwhich is provided in the value field of this TLV.

Example coding for the IUT List Tag ‘80’ is shown in Table 8. In thisexample, unused bytes can be set to a value of ‘FF’.

TABLE 8 1 to 3 IUT Subscription set ID M 3 bytes 4 to 6 1^(st) IUT URI M3 bytes 7 to Y 1^(st) IUT Device Nickname M (Y − 6) byte Y + 1 to Y + 31^(st) IUT Media Token M 3 bytes Y + 4 1^(st) IUT Controller indicationM 1 byte (6n − 2) to (6n) n^(th) IUT URI O 3 bytes (6n + 1) to (Y)nn^(th) IUT Device Nickname O (Y − 6) byte (Y + 1)n to n^(th) IUT MediaToken 3 bytes (Y + 3)n (Y + 4)n n^(th) IUT Controller indication O 1byte

Another exemplary EF includes the EF_(IUTDN) (IUT Device Nickname) shownin Table 9. The EF may be configured to contain the IUT Device Nickname.In this example, the association between an IUT URI and thecorresponding Device Nickname is provided in EF_(AIUTL). Generally, inthis example, coding may be performed using one of the UCS2 code optionsas defined in TS 31.101.

TABLE 9 Identifier: ‘xxxx’ Structure: linear fixed Optional SFI: ‘xx’Record length: X bytes; X ≧ 3 Update activity: low Access Conditions:READ ALWAYS UPDATE ADM ACTIVATE ADM DEACTIVATE ADM Bytes Description M/OLength 1 to X Alpha Identifier M X bytes

Another exemplary EF includes the EF_(IUTMT) (IUT Media Token) shown inTable 10. The EF contains the IUT Media Token. In this example, theassociation between a IUT Device URI and the corresponding Media Tokenis provided in EF_(AIUTL).

TABLE 10 Identifier: ‘xxxx’ Structure: linear fixed Optional SFI: ‘xx’Record length: X bytes; X ≧ 3 Update activity: low Access Conditions:READ ALWAYS UPDATE ADM ACTIVATE ADM DEACTIVATE ADM Bytes Description M/OLength 1 to X IUT Media Token TLV object M X bytes

For this EF, an example IUT Media Token tag is shown in Table 11.

TABLE 11 Description Tag Value IUT Media Token Tag ‘80’

For this EF, example IUT Media Token information is shown in Table 12.

TABLE 12 Description Value M/O Length (bytes) IUT Media Token Tag ‘80’ M1 Length K M Note IUT Media Token — M K Note 1: The length is codedaccording to ISO/IEC 8825.

In this example shown in Table 12, the IUT Media Token Tag ‘80’ may havecontents of IUT Media Token e.g. text, video, audio etc., with codingbeing performed using one of the UCS2 code options as defined in TS31.101, for example.

Another example EF includes the EF_(IUTCONTI) (IUT ControllerIndication) shown in Table 13. The EF may contain the IUT Controllerindications. The association between an IUT URI and the correspondingIUT Controller indication is provided in EF_(AIUTL). The IUT Controllerindication may be provided in text format or in icon.

TABLE 13 Identifier: ‘’ Structure: linear fixed Optional SFI: ‘’ Recordlength: X bytes Update activity: low Access Conditions: READ ALWAYSUPDATE ADM DEACTIVATE ADM ACTIVATE ADM Bytes Description M/O Length 1IUT Controller Indication M 1 byte

In this EF, the indicator status for each indicator type can be 1 bitlong and may be encoded or set as follows. If the bit value is equal to1, set the indication active. If, however, the bit value is equal to 0,set the indication inactive. For example, FIG. 23 is an illustration ofexample indicators with reference bit value position.

Having defined and made available a list of URIs or identities of IUTUEs without additional useful information other than URIs or identitiesof IUT UEs, an IUT UE can gather information about the other identifiedUEs or act unilaterally to modify the list by communicating with the SCCAS, or other components of the network. In one example, an IUTcontroller UE sends SIP OPTIONS to the UEs identified in the list todetermine the capabilities of the other IUT UEs (for example, by usingthe received IUT controller feature tag in the 200 OK response) and todiscover which are currently available, IUT capable and which can havethe IUT controller function transferred to them. The IUT Controllee UEscan obtain the capabilities of the other UEs including the media featuretag that indicates support for IUT controller/controllee functionalityvia a message such as the 200 (OK) response returned in response to amessage such as a SIP OPTIONS request.

Having determined a list of URIs or identities of IUT UEs and optionallyhaving updates to that list, a database in the network e.g. stored inthe SCC AS, HSS etc may store information identifying controller UEs andcontrollee UEs. The information may be stored in any suitable mediumsuch as a computer database or other electronic storage media. Thedatabase may include any appropriate table structure in accordance withsystem requirements. FIG. 21 is an illustration of an exemplarystructure for storing information within the network describingassociated controller and controllee UEs (for example, within a HomeSubscriber Server (HSS)). In FIG. 21, a user A has three devices whichbelong to the IUT set and the device I is an IUT controller. Theremaining devices operate as IUT controllees.

FIG. 22 is an illustration of exemplary information stored in thenetwork such as within an HSS. FIG. 22 shows data for three users, eachunder the same subscription member set. User A and User B have an IUTcontroller function and may setup IUT authorization rules while User Cacts as IUT controllee in the table below.

Within the tables, the subscription set is a set of UEs of the same userfor IUT purposes based on either the same subscription or a differentsubscription that is subject to a roaming agreement. Subscription memberset is a set of UEs between members who are allowed to do Inter-UETransfer and may belong to the same operator's subscription or adifferent operator's subscription subject to a roaming agreement. Withinthe tables, for the IUT UE set, each UE is distinguished as either anIUT controller UE or an IUT controllee UE. Each UE has a device ID, suchas GRUU, Instance ID, or IMEI, that may be mapped with a nickname (e.g.,“Bedroom TV”, “My Mobile”, etc.). Furthermore, for each UE, the tablesdefine a capability to support certain media types and formats for thatUE.

Depending upon the system implementation, information describing thecontroller and controllee UEs may be stored in various networkcomponents e.g. authorization rules may be stored in XDMS and thedocument link to authorization rules stored in XDMS may be stored in thesubscription database. In one example, the link of a media token foreach device or various authorization rules for IUT control are stored inthe database or another network entity.

The network may perform subscription set binding for implementing IUT.The subscription set may be of the same operator or between differentoperators depending on inter-operator agreement (exchanging subscriberinformation and subscriber's device information between the networks).The system may support IUT for the same subscription set. The samesubscription set should be indicated as “Subscription set indication”for IUT on the network and the indication may be provisioned to UEs inmemory (e.g. ME, USIM or ISIM) of the same subscription set.

The network should also have the capability of storing the “lastpreferred configuration”. For example, on an initial call, if the userhas split a video call session between two UE's (voice on the devicehaving ID I and video on the device having ID II). the network can beset to persist this configuration for the subsequent video callresulting in a call termination on multiple UEs.

The network should also have the capability of storing the “last UEwhich acted as a controller”. For example, on an initial communication,a UE-1 has acted as IUT controller function and a UE-2 has acted as IUTcontrollee UE for collaborative sessions. After termination of theinitial communication and establishment of new collaborative sessions,the UE-1 which previously acted as a controller UE becomes a controllerUE based on the information in the network set to persist this lastcontroller UE configuration for the subsequent new communication aftertermination of the previous communication.

When a UE registers with the network the UE will transmit information tothe network that identifies the UE. The registration information mayinclude a request that the UE be assigned controller function within thenetwork. In one example, the UE provides an IMS private identity, IMSpublic user identity and the UE's instance ID to the network foridentification purposes and feature tags as identified earlier that theUE is IUT controller capable. The registration information may beprovided to the SCC AS which can then examine the registrationinformation. The SCC AS may then query the database storing the UE andits subscriber information to determine whether the subscriber and or UEcombination is allowed to be a controller. The database can either belocal or external. An example external database includes an HSS and aninternal one in the SCC AS. The registration information may betransmitted using the Sh interface or ServiceInfo Field via Cxinterface.

By checking the combination of identity information listed above, theSCC AS can determine whether the UE is authorized to be a controller ornot. Accordingly, the SCC AS may check Private ID in this case alldevices are allowed to be controller. the SCC AS may check Private IDand IMEI(s) in this case only devices being used with this private IDcan be controller. Or the SCC AS may check Private ID, IMEI(s), andPublic ID(s) in this case the private ID in combination of device (IMEI)and Public User ID being registered can be controller.

In some implementations, after the UE is registered, the SCC AS providesthe UE with a token, flag, or an indication to be used in subsequent SIPmethods to identify that the UE has been authorized as a controller. Thetoken or indication may be included in a feature tag, new P-header, orXML body. Alternatively, the SCC AS may mark the registration record forthe UE in the SCC AS as being able to be a controller UE. Thus when theUE sends an INVITE or another SIP METHOD the SCC AS may check itsbindings to determine whether the UE is able to perform controllerfunctionality.

The system may also perform an additional check to determine whether adevice in the system is already acting as controller and, when anotherdevice requests controller functionality the system may either rejectthe request and provide an indication to the device (the indication mayinclude an out of band signaling mechanism), or accept the request perthe rules described above.

The controller function for a particular UE may be limited tocontrolling other UEs that are all operated by the same user associatedwith the controller UE. In some implementations of the present system,however, a particular controller UE of one user may have controllerfunction over other UEs belonging to other users where the particularcontroller UE and the other UEs are under the same subscriptionmembership. In that case, a particular UE may provide a mechanism toallow a user to set authorization rules to permit that a controllerfunction can be performed by the target UE which has requested toperform the controller function and the network, such as the SCC AS, orXDMS may process the authorization rules and determine whether to allowthe target UE to perform the controller function. In other to performthe controller function, it may be required for the UE to obtain consentfrom the existing controller UE, or consent of one or more target UEsthat the controller UE has designated. In some cases, any target UEs inthe wireless server may be authorized to perform the controllerfunction. A UE may perform the controller function based upon a temporallimitation, functional limitation (e.g., only allowing for the transferof particular media types), or may be permanent. Any controller UE maybe assigned to set the temporal, functional, or other permission rulesfor transferring controller function to UEs operated by other users.

FIG. 6 illustrates an example flow for providing IUT controller functionto a UE where authorization is only required from a single controllerUE. In step 601 a controllee UE sends a request message to the networkto receive IUT controller function. In step 602 the server (e.g. usingan S-CSCF or SCC AS) looks up the authorization rules stored in theserver itself or in another network entity like XDMS set by thecontroller UE and discovers that there are no temporal, functional, orother limitations that apply to the assignment of IUT controllerfunction and that authorization for the IUT controller assignment onlyneeds to be authorized by the controller UE. In step 603 the networksends a request message to the controller UE to authorize or consent tothe target controllee UE receiving the controller function. In step 604the controller UE sends an OK response if the user of the controller UEaccepts the request. In this step, the user of the controller UE may settemporal/permanent permission. In some cases, these restrictions ontemporal/permanent permission are pre-defined within the network. Instep 605 the server sends an OK response in order to give the controllerfunction to the controllee UE. The OK response in step 604 may bedifferent from that of step 605. The server may include in this responsea) a temporal or permanent password, and b) a token, identifier, orcertificate allowing the target controllee UE to get the controllerfunction. If the target UE receives only temporal permission to act asthe IUT controller, upon releasing or leaving the current session, orexiting from the program which provides a user interface to change somesettings or parameters on controllee UEs, the temporal password maybecome invalid and, thus, the target UE will not retain the IUTcontroller function.

FIG. 7 illustrates an example flow for providing IUT controller functionto a UE where authorization or consent is only required from more thanone controller UE. In step 701 a controllee UE sends the server arequest message to receive IUT controller function. In step 702 theserver identifies the UEs having existing IUT controller function, looksup the authorization rules set by the identified controller(s) anddiscovers that the server needs authorization by or consent of one ormore users (or the user's UE) having IUT controller function. The usermay designate himself and/or other users having a controller function.In step 703 the network sends a request message to the controller UEs toauthorize the target controllee UE to receive IUT controller function.In step 704 the designated user's UE sends an OK response if thedesignated user accepts the request. The designated controller UEs mayset various permission or restrictions when authorizing the provision ofIUT controller function. Alternatively, various temporal, functional, orpermanent permission restrictions may be defined by a user with acontroller UE and be transmitted within the network. In step 705 theserver sends an OK response if all the designated users authorize togive the controller function. The OK response in step 704 may bedifferent from that of step 705. If the controller UEs have setpermission or other restrictions on the provision of IUT controllerfunction, the network includes those restrictions when issuing theauthorization to the target controller UE. If the target UE receivesonly temporal permission to act as the IUT controller, upon releasing orleaving the current session or exiting the program which provides a userinterface to change some settings or parameters on controllee UEs, thetemporal password may become invalid and, thus, the target UE does notretain IUT controller function.

Depending upon the system implementation, the IUT controller UE may bedetermined before session establishment, during a session establishmentprocess, or after a particular session has been established. In somecases, the UE that has the capability to support IUT controllerfunctionality and sends an initial transfer request is initiallyassigned as an IUT controller UE. If the IUT controller UE is determinedbefore session establishment, a UE may request allocation of IUTcontroller function based on the UE's capability to operate as an IUTcontroller UE and associated user preferences. The UE may allow a userto only allocate one UE as an active IUT controller from the list ofavailable URIs or identities for IUT UEs. Different IUT controllersettings could be established for different UEs for the same user. Ifthe IUT controller is assigned at session establishment, a UE may send asession setup request e.g. a SIP INVITE, a SIP re-INVITE or a SIP REFERrequest with an IUT controller feature tag set to “Active”, as describedabove.

In some cases, the SCC AS may ensure that all terminating invitations toa session are routed to a UE that is an IUT controller by including amedia feature tag indicating the IUT controller in an Accept-Contactheader as per RFC 3841.

In some cases, it may be desirable to assign a single IUT-controller UEfor any ongoing session. Accordingly, to ensure that the system onlyassigns a single IUT controller UE, after receiving a request that aparticular UE be assigned the IUT controller function, the network mayverify that the requesting UE is capable of IUT control e.g. a mediafeature tag indicating the IUT controller capability is present in thecontact header, that the requesting UE is authorized to be an IUTcontroller (authorization may be achieved by checking the IMS PrivateUser id associated with the registration of this UE to see if controllerfunctionality is allowed as described above), that there is a policyfrom a network node e.g. SCC AS or Policy Database that only one UEshould become an IUT controller for any ongoing sessions and that thereexists no other allocated IUT controller UEs for the same user. If allthese conditions are met, the network sends a positive response that therequesting UE is to be an IUT controller. The network may send anindication to the other IUT UEs specifying which UE (e.g. using GRUU)has been allocated IUT controller function. This may have been achievedby the UE subscribing to a notification and when a controller has beenassigned a notification is sent to the UE containing the GRUU of thecontroller. If one or more of the conditions above aren't met thenetwork may reject the request. In rejecting the request, the networkmay include a reason code that explains the reason for rejecting therequest.

When registering a particular UE as a controller it may be important toprovide an authentication or authorization mechanism to ensure that onlyauthorized users and/or authorized UEs are allocated controllerfunction. In one example, the IUT subscription is a householdsubscription in addition to a user subscription. The householdsubscription may include a subscription of father, mother and children.In this example, an authorization function in the network may be used tovalidate that a particular UE amongst the household subscription isallowed to be a controller UE. One example network implementationprovides two separate levels of authorization.

First, the network determines whether the device being subscribed isallowed to belong to the same subscription member. This could be as aresult of filter criteria, but then again the SCC AS is the one doingthis, so other filter criteria may send the SIP method to the AS. Theremight be something in the Service Info field from the HSS that goestransparently to the SCC AS which indicates if this is IUT capable as aresult of the UE performing a SIP REGISTRATION. For example, in somecases, there may be information in the SCC AS that determines whetherthe device being subscribed is capable of performing the controllerfunction. Alternatively, the information may be provided via an IMSI orPrivate identity. For example, all family members belong to the samePerson Network, but only dad has the ability to set a device as acontroller over the other devices of mother and children.

Second, the SCC AS determines whether the registering UE is allowed tobecome an IUT controller. This may be done by checking the GRUUinformation for the UE being registered. This information again may bestored within the HSS or SCC AS, whereby the subscriber indicates whichdevice can be a controller. Alternatively, it may be possible to linkthe whole information to the registration message, in that when a UEregisters there will be a private ID. The private ID may be used todetermine whether the UE has the ability to use IUT or not. There may becapabilities such as IMSI private ID can be: “assign controller” or, “becontrolled”. So any UE that comes from a private user ID with “assigncontroller” is allowed to set-up that UE as a controller

IMS private IDs that are able to access an IRS can have certainprofiles, for example, a household subscription may contains 4 IMSprivate IDs, dad, mom and 2 kids. Dad is only one that is allowed toassign a controller. These are all the same subscription member, whichmay be called a subscription member set.

Assuming that 2 IMS private IDs can assign controller for the group onemust have override authority or if you are allowed to be controller, youare notified if another UE becomes the controller. If you are currentlythe controller you can deny the change or allow the change. Thisrequires subscribing to a status notification within the network and,upon receiving notification that the network has a particular policy, toask the other controller if controlling capabilities can be changed.

The IUT controller UE can be determined before session establishment,during session establishment or when requesting an IUT controllertransfer function to another UE. When determining the IUT controller UEbefore session establishment, a UE sends a request to have IUTcontroller function based on the UE's capability and user preferences.The UE may allow a user to make more than one UE an active IUTcontroller from the list of URIs or identities for IUT UEs. Whendetermining the IUT controller UE during session establishment and whenrequesting an IUT controller function transfer to another UE by any IUTcontroller capable UE, a UE sends a request such as a SIP INVITE, a SIPre-INVITE or a SIP REFER request with a media feature tag indicating theIUT controller function. The media feature tag could be an IMSCommunication Service Identifier (ICSI) value or IMS ApplicationReference Identifier (IARI) value that identifies the IUT controllerfunction to be transferred. When the network receives the request, thenetwork checks that the requesting UE is capable to be an IUTcontroller, that the requesting UE is authorized to be an IUT controller(authorization is achieved, for example, by checking the IMS PrivateUser id associated with the registration of this UE to see if controllerfunctionality is allowed), and that there is a policy (e.g. from PolicyDatabase) that multiple UEs are to become an IUT controller for anyongoing sessions or for the same collaborative session.

If all these conditions above are met the network sends a positiveresponse that the requesting UE is to be an IUT controller. The networkmay send to the other IUT UEs an indication that which UE (e.g. usingGRUU information) is an IUT controller. If one or more than one of theconditions above are not met the network may reject the request andoptionally provide a reason code for explaining the reason the requestwas rejected.

Having been established as an IUT controller UE, the controller UE mayissue requests to the network to transfer media types to certaincontrollee UEs, or to transfer IUT-controller function to other UEs. Inorder for the IUT controller UE to transfer media and/or controllerfunction to a controllee UE, the IUT controller UE sends a message suchas a SIP REFER request to the network e.g. SCC AS. The SIP REFER requestmay contain embedded within the URI in the REFER-TO header anothermessage such as at least some of the SIP headers and/or SDP contents ofthe SIP INVITE request or SIP Re-INVITE request that the SCC AS is tosend to the controllee UE identified by the URI in the Refer-To header.The SIP INVITE request or SIP RE-INVITE request that is sent to thecontrollee UE may contain data identifying the media types to betransferred to the controllee UE. To allow the controllee UE todetermine that control is being transferred to it, the SIP INVITErequest also includes an identifier that identifies the IUT controllerfunction. This identifier may include a) a URI that identifies the IUTcontroller function in a SIP header field, b) a New SIP URI parameter(i.e. IUT controller URI parameter) in the Request-URI or in the URI inthe TO header, c) a Media Feature tag that indicates IUT controller tobe included in an Accept-Contact header (as per RFC 3841), d) an IMSCommunication Service Identifier (ICSI) value or IMS ApplicationReference Identifier (IARI) value that identifies the IUT controllerfunction should be transferred such as “g.3gpp.app_ref” feature tag tobe included in an Accept-Contact header (NOTE that the UE willpreviously at registration have registered the Media Feature tag in theContact header of the SIP REGISTER request as per RFC 3840), or e) a newSIP header field (e.g. a P-Header according to RFC 3427) that indicatesthe IUT controller function is transferred. In another implementation,the 3.gpp.iut feature tag can be extended with additional options toidentify that controller function is being transferred. An exampleembodiment is included below in Table 14.

TABLE 14 Media feature-tag name: g.3gpp.iut ASN.1 Identifier:1.3.6.1.8.2.y Summary of the media feature indicated by this tag: Thisfeature-tag indicates that the device has IUT capabilities. Valuesappropriate for use with this feature-tag:active, controller,controllee, controllertransfer. The feature-tag is intended primarilyfor use in the following applications, protocols, services, ornegotiation mechanisms: This feature-tag is most useful in acommunications application, for describing the capabilities of a device,such as a phone or PDA. Examples of typical use: Indicating that amobile phone supports IUT functionality. Controllertransfer identifiesthat the UE wants to transfers its controlling capabilities

Other embodiments could also include that when the UE performs therequest to transfer controller functionality the UE sets the mediafeature tag to controllee. When the SCC AS receives the request the SCCAS will check the status of the UE the message has been received from.If the status of the UE is assigned as a controller the UE will knowthat the UE is wanted to pass on controller functionality to the targetdevice identified in the message. When the SCC AS sends the message tothe target device the message may include a token or identifer thatidentifies that controller functionality is being assigned to the UE.

The following examples in FIG. 8 illustrate flows for transferringIUT-controller function and/or media types from a first controller toanother UE as requested by an IUT controller UE. In the examples, UE-1has an established multimedia session with a Remote party, which isanchored at an SCC AS. The multimedia session contains two mediacomponents (Media-A and Media-B) and UE-1 wants to transfer thecollaborative session control and one of the media types (media-A) toanother UE-2. In the examples, UE-1 and UE-2 may have registered usingthe same access network bearer or a different network access bearer.UE-1 and UE-2 may use different Internet Protocol-Connection AcrossNetworks (IP-CAN) e.g. 3GPP IP-CAN on UE-1 and non-3GPP IP-CAN on UE-2.The anchored SCC AS or another network entity may determine what bearerto use for each UE. It is assumed that UE-1 and UE-2 belong to the samesubscriber.

Whenever the UE acquires IP connectivity via an IP CAN, the UE canregister in the IMS as defined in TS 23.228. In that case, the userprofile contains a C MSISDN which is bound to the IMS Private UserIdentity. The S-CSCF may follow the procedures defined in TS 23.218 forperforming 3rd party registration towards the SCC AS. When using CSaccess for media, the UE may be registered in IMS as specified in TS23.292. When registering in the IMS as defined in TS 23.228 the UE mayindicate its capability to support controller or controlee functionalityfor IUT. An example SIP REGISTER request for the S-CSCF to perform 3rdparty registration towards the SCC AS is shown below in Table 15.

TABLE 15 REGISTER sip: sccas.home1.net /2.0 Via: SIP/2.0/UDPscscf1.home1.net;branch=z9hG499ffhy Max-Forwards: 70P-Access-Network-Info: 3GPP-UTRAN-TDD; utran-cell-id- 3gpp=234151D0FCE11From: <sip:scscf1.home1.net>; tag=538ya To:<sip:user1_public1@home1.net> P-Access-Network-Info: IEEE-802.11bCall-ID: 1asdaddlrfjflslj40a222 Contact: <sip:scscf1.home1.net>;expires=600000 CSeq: 87 REGISTER Content-Type: multipart/mixed;boundary=“boundary1” Content-Length: (...) --boundary1 Content-Type:message/sip REGISTER sip:registrar.home1.net SIP/2.0 Via: SIP/2.0/UDPpcscf1.visited1.net;branch=z9hG4bK240f34.1, SIP/2.0/UDP[5555::aaa:bbb:ccc:eee]:1357;comp=sigcomp;branch=z9hG4bKnashds7Max-Forwards: 69 P-Access-Network-Info: IEEE-802.11b Path:<sip:VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@pcscf1.visited1.net;lr;ob>Require: path P-Visited-Network-ID: “Visited Network Number 1”P-Charging-Vector: icid-value=“AyretyU0dm+602IrT5tAFrbHLso=023551024”From: <sip:234150999999999@ics.mnc015.mcc234.3gppnetwork.org>;tag=2hiueTo: <sip:234150999999999@ics.mnc015.mcc234.3gppnetwork.org> Contact:<sip:[5555::aaa:bbb:ccc:eee];comp=sigcomp>; reg-id=2; +sip.instance=“<urn:gsma:imei:90420156-025763-0>;+g.3gpp.icsi- ref=”urn%3Aurn-7%3gpp-service.ims.icsi.mmtel”;+g.3gpp.ics=“principal”;+g.3gpp.icsflow=“WLAN”;expires=600000 Call-ID: apb03a0s09dkjdfglkj49111 Authorization: Digestusername=“user1_private@home1.net”, realm=“registrar.home1.net”,nonce=base64(RAND + AUTN + server specific data), algorithm=AKAv1-MD5,uri=“sip:registrar.home1.net”,response=“6629fae49393a05397450978507c4ef1” CSeq: 3 REGISTER Supported:path, outbound, gruu Content-Length: 0 --boundary1 Content-Type:message/sip SIP/2.0 200 OK Via: SIP/2.0/UDPicscf1_p.home1.net;branch=z9hG4bK351g45.1, SIP/2.0/UDPpcscf1.visited1.net;branch=z9hG4bK240f34.1, SIP/2.0/UDP[5555::aaa:bbb:ccc:eee]:1357;comp=sigcomp;branch=z9hG4bKnashds7 Path:<sip:term@pcscf1.visited1.net;lr;ob> Service-Route:<sip:orig@scscf1.home1.net;lr> From:<sip:234150999999999@ics.mnc015.mcc234.3gppnetwork.org>;tag=2hiue To:<sip:234150999999999@ics.mnc015.mcc234.3gppnetwork.org> Call-ID:apb03a0s09dkjdfglkj49111 Contact:<sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp>;pub-gruu=“sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6”;temp-gruu=“sip:tgruu.7hs==jd7vnzga5w7fajsc7-ajd6fabz0f8g5@example.com;gr”;+sip.instance=“<urn:gsma:imei:90420156-025763-0>”;+g.3gpp.icsi-ref=“urn%3Aurn-7%3gpp-service.ims.icsi.mmtel”;+g.3gpp.ics=“principal”;+g.3gpp.icsflow=“WLAN” ;expires=600000 Supported: path, outbound Require:outbound Date: Wed, 11 July 2001 08:49:37 GMT P-Associated-URI:<sip:user1_public2@home1.net>, <sip:user1_public3@home1.net>,<sip:+1-212-555-1111@home1.net;user=phone> CSeq: 3 REGISTERContent-Length: 0 --boundary1--

FIG. 8 illustrates a flow for transferring IUT-controller function to aUE as requested by an IUT-controller UE. In step 801 UE-1 decides totransfer the collaborative session control and media type (media-A) toUE-2. UE-1 sends a request to the SCC AS, indicating that the currentcollaborative session control and media type (Media-A) will betransferred to UE-2. In step 802 the SCC AS (or any other networkcomponent) identifies the transfer request, verifies that UE-2 isallowed and capable to act as a controller, verifies that UE-2 hasregistered appropriate capabilities e.g. feature tags per RFC 3840,determines what bearer to use for UE-2 based on the device capability,user preference and/or policy in the network, and determines whether theselected bearer has been registered by UE-2. In step 803 the SCC ASgenerates and sends UE-2 a session establishment request message usingGm or I1 reference point, or other data transfer methods indicating thatthe collaborative session control and media type (Media-A) are to betransferred. In step 804 a collaborative session control is establishedbetween UE-2 and the SCC AS. UE-2 becomes the controller UE for theestablished collaborative session. In step 805 a session forcommunicating mediate type (Media-A) between UE-2 and the remote partyis established. At this time, the remote leg is updated accordingly.After the successful establishment of the collaborative session controland media type (Media-A) on UE-2, the SCC AS sends UE-1 a responsemessage to the transfer request message or another message notifyingUE-1 of the result of the transfer request message in step 806 (forexample, a SIP NOTIFY request that is sent for a final response receivedas a result of a SIP REFER request as per RFC 3515). Finally, in step807 the previous media type (Media-A) session on UE-1 may be releasedand the collaborative session control is released. At this time UE-1becomes a controllee UE.

FIG. 9 illustrates a flow for transferring IUT controller functionalityfrom UE-1 to UE-2 where the incoming session request is delivered overthe Gm reference point and the media is transmitted via acircuit-switched network. An MSC server enhanced ICS could be anexemplary entity of an Interworking entity for implementing theillustrated flow. Alternatively, the Interworking entities may consistof a legacy MSC server and MGCF. When the interworking entitiescorrespond to MSC Server and MGCF, the CS bearer setup procedures followthe steps 11-17 in the FIG. 7.4.2.2.2-2 of TS 23.292.

With reference to FIG. 9, in steps 901 and 902 UE-1 decides to transferthe collaborative session control and media-A to UE-2. Accordingly, UE-1sends a request to the SCC AS via IMS entities, indicating that thecurrent collaborative session control and Media-A will be transferred toUE-2. In this example, an IUT controller UE can initiate a transferrequest such as via SIP REFER by transmitting a request having thefollowing information: 1) Source UE (may be included within the Fromheader field, a P-Asserted-Identity header field or P-Served-User headerfield), 2) Target UE (may be included within the Refer-To header field),3) IUT controller transfer indication (may be included within theAccept-Contact header field, e.g. embedded in the INVITE request orembedded in the Refer-To header field), 4) Target-Dialog-ID (may beincluded within the Target-Dialog header field containing an existingdialog identifier if the Target UE is already part of the collaborativesession, and no Target-Dialog-ID when this is a new session for theTarget UE), and 5) Media type (e.g. audio, video, file etc (e.g.,included in Refer-To header field).

In step 905, the SCC AS identifies the request (e.g the SIP REFERrequest), verifies that the UE-2 is allowed and capable to act as acontroller, verifies that UE-2 has registered appropriate capabilitiese.g. feature tags per RFC 3840, what bearer to use for the UE-2 based onthe device capability, user preference and/or policy in the network, andwhether the selected bearer has been registered by the UE-2. If UE-2 isnot allowed to act as a controller, the SCC AS may reject the request.If UE-2 refuses the collaborative session control transfer, a suitableresponse indicating the refusal is sent. The response may indicate thereason for refusing the transfer. Such a response may be a SIP 488 (NotAcceptable Here) response when the Media Types or Codecs offered are notacceptable. A warning may be included in the response indicating thereason for failure. The message to UE-1 indicating failure of thetransfer may be contained in a SIP NOTIFY request containing in the bodya SIPfrag of the response from UE-2 (e.g., a SIP 488 (Not AcceptableHere) response).

In steps 906 and 907, if the message received in step 905 contains amedia transfer for audio or video then the SCC AS generates and sendsUE-2 a session establishment request message. The session establishmentrequest message such as SIP INVITE request or SIP re-INVITE sentsubsequent to receiving a SIP REFER includes the followinginformation: 1) Source UE (may be included within the Referred-By headerfield and P-Asserted-Identity header field, P-Preferred-Identity headerfield or P-Served-User header field), 2) Target UE (may be included inthe To header field and Request-URI field), 3) IUT controller transferindication (may be included in the Accept-Contact header field), 4)Target-Dialog (may be included in the Target-Dialog header fieldcontaining an existing dialog if the Target UE already is part of thecollaborative session and no Target-Dialog when this is a new sessionfor the Target UE), and 5) Media type (e.g Audio, Video, file) (may beincluded in the SDP embedded in the INVITE request). The request mayalso include a PSI DN to be used for the CS Call set that identifiesthis session. If the SDP contains M line that allows the bearer to besetup over CS, then, in step 910, UE-2 sends a CS call setup message tothe Interworking entities using the PSI DN as the B number. In step 911the Interworking entities such as an MSC server enhanced for ICSresponds with a call proceeding message and begins to setup the CSBearer Control Signaling Path. In steps 912 and 913 the Interworkingentities send a SIP INVITE towards the SCC AS via IMS entities. When SCCAS receives the INVITE at step 913 the SCC AS may use the PSI DN toretrieve the session information and in step 916, when the Interworkingentities receive a SIP 200 OK from the SCC AS via IMS entities, theInterworking entities map the received SIP 200 OK response to a CONNECTmessage and send it to UE-2. In step 917, when receiving the CONNECTmessage, the UE-2 sends a CONNECT ACK message to the Interworkingentities. In step 920 the UE-2, Interworking entities and SCC AScomplete the setup of the CS Bearer Control Signaling Path.Collaborative session control between UE-2 and the SCC AS isestablished. UE-2 becomes the controller UE for the establishedcollaborative session. In step 921 exchange of media type (Media-A)communication between UE-2 and the remote party is established. At thistime the remote leg is updated accordingly if SDP information needs tobe changed. In steps 922 and 923, after the successful establishment ofthe collaborative session control and media type (Media-A) on UE-2, theSCC AS sends UE-1 a response message to the transfer request message ora message notifying the result of the transfer request message usingsuch as SIP NOTIFY. Finally, in step 926 the previous media type(Media-A) session on UE-1 may be released and the collaborative sessioncontrol is released. UE-1 becomes a controllee UE. Note that in theabove example steps involving the communication of conventionalacknowledgement messages are not described. If transferring all mediaflows on the UE-1 to UE-2, the existing session on the UE-1 may bereleased.

FIG. 10 illustrates a flow for transferring IUT controller functionalityand media from UE-1 to UE-2, where the incoming session is deliveredover the I1 reference point and the media is transmitted via a CSnetwork. In one implementation, an MSC server enhanced ICS could be anexemplary entity of the Interworking entity. Alternatively, theInterworking entities may consist of a legacy MSC server and MGCF. Whenthe interworking entities correspond to MSC Server and MGCF, the CSbearer setup procedures follow the steps 1011-1017 in the FIG.7.4.2.2.2-2 of the TS 23.292.

In steps 1001 and 1002 UE-1 decides to transfer the collaborativesession control and media-A to UE-2. Accordingly, UE-1 sends a requestto the SCC AS via IMS entities, indicating that the currentcollaborative session control and Media-A will be transferred to UE-2.In one implementation UE-1 sends a transfer request such as via SIPREFER method with following information: 1) Source UE (may be includedwithin the From header field, a P-Asserted-Identity header field, orP-Served-User header field), 2) Target UE (may be included within theRefer-To header field), 3) IUT controller transfer indication (may beincluded within the Accept-Contact header field, e.g. embedded in theINVITE request or embedded in the Refer-To header field), 4)Target-Dialog (may be included within the Target-Dialog header fieldcontaining an existing dialog identifier if the Target UE is alreadypart of the collaborative session and no Target-Dialog when this is anew session for the Target UE), and 5) Media type (e.g. audio, video,file etc.) (may be included in the Refer-To header field).

In step 1005, the SCC AS identifies the request (e.g the SIP REFERrequest). If UE-2 is SIP Registered in SCC AS, the SCC AS verifies thatthe UE-2 is allowed and capable to act as a controller, verifies thatUE-2 has registered appropriate capabilities e.g. feature tags per RFC3840, determines what bearer to use for the UE-2 based on the devicecapability, user preference and/or policy in the network, and determineswhether the selected bearer has been registered by the UE-2. If UE-2 isnot allowed to act as a controller, the SCC AS may reject the request.If UE-2 refuses the collaborative session control transfer, a suitableresponse indicating the refusal and optionally the reason for refusal issent.

In step 1006, the SCC AS has determined that UE-2 is not reachable by Gmreference point. This may be, for example, because the UE has no activeSIP registration, in another example, UE-2 may be SIP Registered but theSCC AS has been informed via the I1 protocol that Gm reference point isnot available. Providing the message received in step 1002 contains SDPline for audio or video then the SCC AS then generates and sends UE-2 anincoming call request message via the I1 reference point including anindication of IUT controller functionality and an indication to triggerthe UE-2 to establish the bearer setup, if the UE-2 hasn't establishedthe selected bearer yet, using transport mechanisms such as but notlimited to: USSD, SMS, MBMS, CellBroadcast, IP pipe running over GPRS inGERAN, UTRAN, LTE, WLAN, WiMax, or CDMA2000.

In step 1007, the UE-2 sends a CS call setup message to the Interworkingentities and in step 1008 the Interworking entities respond with a callproceeding message and begin to set up the CS Bearer Control SignalingPath. In steps 1009 and 1010 the Interworking entities send a SIP INVITEtowards the SCC AS via IMS entities. In step 1013, when the Interworkingentities receive a SIP 200 OK from the SCC AS via IMS entities, theInterworking entities map the received SIP 200 OK response to a CONNECTmessage and send it to UE-2.

In step 1014, when receiving the CONNECT message, the UE-2 sends aCONNECT ACK message to the Interworking entities and in step 1017 theUE-2, Interworking entities and SCC AS complete the setup of the CSBearer Control Signaling Path. At this point, the collaborative sessioncontrol between UE-2 and the SCC AS is established. UE-2 becomes thecontroller UE for the established collaborative session.

In step 1018 media type (Media-A) between UE-2 and the remote party isestablished. At this time the remote leg is updated accordingly. Insteps 1019 and 1020, after the successful establishment of thecollaborative session control and media type (Media-A) on UE-2, the SCCAS sends UE-1 a response message to the transfer request message or amessage indicating the result of the transfer request message using suchas a SIP NOTIFY message. In step 1023 the previous Media-A on UE-1 maybe released and the collaborative session control is released. At thistime UE-1 becomes a controllee UE. Note that in the above example stepsinvolving the communication of conventional acknowledgement messages arenot described. If transferring all media flows on the UE-1 to UE-2, theexisting session on the UE-1 may be released.

The above examples describe flows that result in a successful transferof IUT-controller function or media to an eligible controller capableUE. If the transfer is not successful, however, the system may sendvarious message response reason codes or indications to the requestingUE that provide an explanation of why the transfer failed. Exampleresponse reason codes or indications include: no IUT controllercapability (so a legitimate request for controller status cannot be madeby that UE), there is already an IUT controller UE for the session (incases where only a single UE can be an IUT controller, for example), UEis not under the same subscription, max limit of IUT controllers,unavailable (not registered, no battery, etc.), unauthorized to be anIUT controller, unsupported media type, unsupported media format, notallowed to establish a new session because of max number of simultaneoussessions is already reached, busy, etc. The response reason codes orindications may be contained within a SIP Warning header included in theresponse. In some cases, the rejection response and associated reasoncodes or indications may be included in the body of a SIP NOTIFY requestsuch as within a SIPfrag containing part of the response messagereceived at the SCC AS or other network node.

During operation of the present system, an IUT controller UE maysubscribe to receive notifications that describe the ongoing sessions ona particular UE or all the UEs associated with the user. Thenotifications may identify various ongoing sessions and their associatedcontrollee and/or controller UEs. In one example, a user A has initiatedtwo sessions; one with user C and user D, and another with user B. Withreference to the session with users C and D, user A has three sessionsfor his IUT controller UE set (i.e. devices 1, 2 and 3). For theconversation with user B, user A has two sessions on his IUT UE set(i.e. devices 2 and 3). In this example, user A may wish to knowinformation describing currently ongoing sessions associated with theuser's IUT UEs. In that case, user A may send a request (e.g. SIPSUBSCRIBE) and gets a response (e.g. SIP NOTIFY) with the followinginformation set per Target-Dialog using the dialog event package asdescribed in RFC 4235:

-   -   Target-Dialog    -   Participating user's ID (SIP URI, TEL URI, or nickname)    -   IUT device ID/Nickname    -   IUT controller device ID/Nickname    -   Media type or file per session (i.e. a notification that there        are three different sessions on the user A's devices for a        particular collaborative session)

As illustrated in the example shown in FIG. 11, multiple UEs may existfor user A for all ongoing sessions. User A's device 60 has issued atransfer request to user A's device 64 for the collaborative session Xinvolving communication with user C's devices 68 or 70 and user A'sdevice 62 has sent a transfer request to user A's device 64 for thecollaborative session Y involving communication with user B's device 66.When a new invitation for a new media type is received on user A'sdevice 62, it is possible to send a media transfer request or redirectrequest using user A's device 60 in order to transfer the new invitationto user A's device 64. If the media transfer request or redirect requesthas been successfully accepted, the success notification is transferredto the controller UEs for the session or all IUT controller UEs whichare user A's device 60 and 62. Depending on user preference and devicecapability, a user may configure to receive notifications on allcontroller UEs or assign which controller UE to receive notificationsamong multiple controller UEs rather than receiving notifications to allcontroller UEs. As shown in FIG. 11, although multiple UEs exist foruser A, only one IUT controller UE exists for each collaborativesession. As such, only the controller UE for the particularcollaborative session receives a notification when the session statushas changed on that particular collaborative session.

In some implementations there may be a substantial amount ofnotification traffic eligible to be transmitted to any controller UE(s).Filtering mechanisms may be implemented within the notificationmechanism on the network and/or each individual UE to optimize thevolume of notification traffic being transmitted to the controlling UEs.

For terminating sessions, in one implementation of the present system,whichever UE first receives the request for the session establishmentand is able to accept the session establishment request may be allocatedthe controller function (otherwise the UE which has accepted the sessionwill be stuck on the session and will not have the ability to send atransfer request to another UE of the user). On receiving an initialsession establishment request (e.g. a SIP INVITE, SIP re-INVITE, or SIPUPDATE) from the remote party, the network may need to ensure that therequest is routed to a UE that is a controller and or supports thecontroller function. Once a session has been established, theterminating user may want to transfer collaborative session control toanother UE of the same user. If the target UE does not have IUTcontroller capability and is not an IUT controller UE then the target UEis unable to make a transfer request to another UE. In some cases,however, the transfer may still take place. For example, a UE may allowa user to provide a redirect setting on the network i.e. for redirectingthe request to a particular UE, such as a controller UE assigned by auser, when an invitation request arrives in the terminating side. Inaddition, a UE may allow a user to setup a user preference to indicatewhich bearer to use for session establishment, possibly as a combinationof media type, and device capability. For example a user having two UEsmay setup a user preference to use a packet switched bearer for speechtype sessions on UE-1 and to use a circuit switched bearer for videotype sessions on UE-2.

Alternatively, if there is no redirect setting, when the terminatingnetwork receives an invitation request, the network sends a request toask the user whether to accept the invitation on the UE or redirect toanother UE (i.e. a controller UE). If the user decides to redirect toanother UE (which is a controller UE) then the network sends a responsecontaining the transferred UE identity to the terminating network andthe terminating network sends the invitation request to the UE assignedby the user.

Alternatively, if there is no redirect setting, when the terminating UEreceives an invitation request, the UE asks the user whether to acceptthe invitation or redirect to another UE. If the user decides toredirect to another UE (i.e. a controller UE) then the network sends aredirect request to the terminating network. In that case, theterminating network sends the invitation request to the UE assigned bythe user. When the terminating network receives (e.g. via the SCC AS) aninvitation message (e.g. a SIP INVITE, SIP re-INVITE, or SIP UPDATE) theterminating network determines which terminating UE to become an IUTcontroller based on device capability, user preference and/or policy,and which bearer to use for the terminating UE. The network checks thatthe terminating UE has registered for the identified bearer. If not, thenetwork may send an indication to the terminating UE to initiate bearerregistration. After successful bearer registration, the network (e.g.,via the SCC AS) sends an invitation request message (e.g. SIP INVITE)indicating that the session control and certain media types arepresented to the target terminating UE. On receiving an Ack or OKresponse message, the SCC AS may send an indication to the Remote partythat the media stream has been redirected to a different UE.

FIGS. 12 a and 12 b illustrate a flow for terminating collaborativesession establishment when a remote party sent a session invitationrequest. In one implementation, an MSC server enhanced ICS could be anexemplary entity of the Interworking entity. Alternatively, theInterworking entities may consist of a legacy MSC server and MGCF. Theexample flow assumes that UE-1 has setup a device capability/userpreference to be an IUT controller and to use PS bearer for sessionestablishment with video type. UE-2 has setup a device capability/userpreference to use CS bearer for session establishment with a speechmedia type. FIG. 12 a shows a high level flow, as follows. In step 1101,the terminating network (e.g. SCC AS) receives an invitation message(e.g. a SIP INVITE or SIP re-INVITE). In step 1102, the SCC ASdetermines which terminating UE to become an IUT controller based ondevice capability, user preference and/or policy, and which bearer touse for the terminating UE based on device capability, user preferenceand/or policy. In the example, the SCC AS determines UE-1 acts as an IUTcontroller and uses PS bearer with a video media type while UE-2 uses CSbearer with a speech media type. In steps 1103 and 1104 the SCC AS sendsthe invitation request message (e.g. SIP INVITE) to the Interworkingentities via IMS entities in order to establish a collaborative sessiontoward UE-2. In step 1105, the Interworking entities send a CS callsetup message to the UE-2. In step 1106, the UE-2, Interworking entitiesand the SCC AS complete the setup of the CS Bearer Control SignalingPath and the SCC AS and remote party complete the remote legestablishment. The Collaborative Session with speech media type betweenUE-2 and the SCC AS is established the remote leg between the SCC AS andremote party is established.

In steps 1107 and 1108, the SCC AS sends an invitation request message(e.g. SIP INVITE) to UE-1 via IMS entities. In step 1109, thecollaborative session with video media type between UE-1 and the SCC ASis established and the remote leg between the SCC AS and remote party isupdated. The UE-1 gets a Collaborative Session control which allowsapplying IUT transfer request.

In the steps illustrated in FIG. 12 a, in one implementation it isassumed that UE-1 and UE-2 belong to the same subscriber (i.e. the samesubscription set) and the SCC AS determines to establish CollaborativeSessions over CS network on the UE-2 and over PS network on the UE-1which keeps Collaborative Session Control. In some cases, when theinterworking entities correspond to MSC Server and MGCF the CS bearersetup procedures follow the steps 11-17 in the FIG. 7.4.2.2.2-2 of theTS 23.292.

FIG. 12 b illustrates more detail flow than in FIG. 12 a as follows: Instep 1201, the terminating network (e.g. SCC AS) receives an invitationmessage (e.g. a SIP INVITE or SIP re-INVITE). In step 1202, the SCC ASdetermines which terminating UE to become an IUT controller based ondevice capability, user preference and/or policy, and which bearer touse for the terminating UE based on device capability, user preferenceand/or policy. In the example, the SCC AS determines UE-1 acts as an IUTcontroller and uses PS bearer with a video media type while UE-2 uses CSbearer with a speech media type. In steps 1203 and 1204 the SCC AS sendsthe invitation request message (e.g. SIP INVITE) to the Interworkingentities via IMS entities in order to establish a collaborative sessiontoward UE-2. In steps 1205 and 1206, the Interworking entities send a CScall setup message to the UE-2 and receive a CS call connection message.In steps 1207 through 1209, a SIP 200 OK response message is sent toRemote Party via IMS entities and SCC AS. The remote party sends SIP ACKtoward the Interworking entities in steps 1210 through 1212 and theInterworking entities send a CONNECT response message to UE-2. In step1214 a session with a speech media type between UE-2 and the Remoteparty is established.

In steps 1215 through 1217 the SCC AS sends the invitation requestmessage (e.g. SIP INVITE) to the terminating UE-1 to establish a sessionwith a video media type. At this point, the collaborative sessioncontrol with SCC AS is established and the terminating UE-1 becomes anIUT controller. On receiving a SIP 200 OK response from UE-2 via theInterworking entities and IMS entities as shown in steps 1218 through1220, the SCC AS sends a SIP UPDATE to the remote party to update theremote leg in step 1221. After successful SIP responses in steps 1222through 1225, in step 1226 a collaborative session with the video mediatype between UE-1 and the SCC AS is established and the remote legbetween the SCC AS and the Remote party is updated. Note that in theabove example steps involving the communication of conventionalacknowledgement messages are not fully described.

FIG. 13 illustrates a flow for transferring IUT Controller functionalityfrom PS UE-1 to PS UE-2. UE-1 and UE-2 may use the same bearer ordifferent bearers. Even if using a Packet Switched bearer on UE-1 andUE-2 it may be possible to use 3GPP IP-CAN on UE-1 and non-3GPP IP-CANon UE-2. In steps 1301 and 1302, UE 1 decides to transfer thecollaborative session control and media-A to UE 2. Accordingly, UE-1sends a request to the SCC AS via IMS entities, indicating that thecurrent service control and media type (Media-A) will be transferred toUE 2. In step 1305, the SCC AS identifies the request e.g the SIP REFERrequest, verifies that the UE-2 is allowed and capable to act as acontroller and determines PS bearer used for the UE-2 based on thedevice capability, user preference and/or policy in the network.

In steps 1306 and 1307, the SCC AS generates and sends a sessionestablishment request message such as a SIP INVITE request (or SIPre-INVITE) indicating the collaborative session control and media type(Media-A). The session establishment request can be routed over thedesired access leg (bearer) using the flow identifier media feature tagin the Accept-Contact header described above. In step 1312, thecollaborative session control between UE 2 and the SCC AS isestablished. UE 2 becomes the controller UE for the establishedcollaborative session. In step 1313, media type (Media-A) communicationbetween UE 2 and remote party is established. The remote leg is updatedaccordingly. In steps 1314 and 1315, after the successful establishmentof the collaborative session control and media type (Media-A) on UE 2,the SCC AS sends UE 1 a response message to the transfer request messageor a message notifying the result of the transfer request message suchas SIP NOTIFY message. In step 1318, the previous media type (Media-A)on UE 1 and the Collaborative Session control may be released. UE 1becomes a controllee UE. Note that in the above example steps involvingthe communication of conventional acknowledgement messages are notdescribed.

The present system and method may be used to provide an IUT controllertransfer application. An example method implemented by the presentsystem indicates at least one of the ability to perform the IUTController function and inability to perform the IUT Controllerfunction. The method includes providing in a Session Initiation Protocol(SIP) message an indication of the ability to support the IUT:Controllerfunction, and providing in a Session Initiation Protocol (SIP) messagean indication of the inability to support the IUT:Controller function.The indication of at least one of the ability to perform the IUTController function and inability to support the IUT:Controller functionmay be indicated using a Media Feature Tag. The Media Feature Tag mayindicate at least one of the values “Active” indicating the ability toact as an IUT controller and is currently acting as the IUT controllerfor a collaborative session, “Inactive” indicating the ability to act asan IUT controller but is not currently acting as the IUT controller fora collaborative session, and “Passive” indicating the inability to actas an IUT controller for a collaborative session.

Depending upon implementation, the Media Feature Tag may be containedwithin a Contact Header. The Session Initiation Protocol (SIP) messagemay include one of a SIP REGISTER request, a SIP INVITE request, a SIPRe-INVITE request, a SIP UPDATE request, a SIP PRACK request, a SIPREFER request, a SIP PUBLISH request, a SIP MESSAGE request, a SIPSUBSCRIBE request, a SIP NOTIFY request, a SIP OPTIONS request, and aSIP response.

An example method of transferring IUT controller function from onedevice to another may include providing in a Session Initiation Protocol(SIP) message an indication of the transfer of the IUT:Controllerfunction. The indication of the transfer of the IUT:Controller functionmay be indicated using a Media Feature Tag. The Media Feature Tag may becontained in an Accept-Contact Header. The Session Initiation Protocol(SIP) message may be one of a SIP INVITE request, a SIP Re-INVITErequest, a SIP UPDATE request, a SIP PRACK request, a SIP REFER request,a SIP PUBLISH request, a SIP MESSAGE request, a SIP SUBSCRIBE request, aSIP NOTIFY request, a SIP OPTIONS request, and a SIP INFO Request. TheMedia Feature Tag may be contained in an Accept-Contact Header that isitself contained within a Refer-To header.

The method may include receiving, in response, an indication of one ofSuccessful IUT Transfer, or Unsuccessful IUT Transfer. The indicationmay include a SIP Response, a SIP UPDATE request, a SIP PRACK request, aSIP NOTIFY Request, a SIP PUBLISH Request, a SIP MESSAGE Request, a SIPOPTIONS request, or a SIP INFO Request. Alternatively, the indicationmay be one of a Media feature tag in a Contact header, within the bodyof a SIP request or SIP response, within a SIPfrag in a body of a SIPrequest or SIP response, or encoded in an XML format.

Alternatively, the method may provide for transferring IUT controllerfunction from one point of attachment to another point of attachment.The point of attachment technology may include IEEE-802.11,IEEE-802.11a, IEEE-802.11b, IEEE-802.11g, IEEE-802.11n, 3GPP-GERAN,3GPP-UTRAN-FDD, 3GPP-UTRAN-TDD, 3GPP-E-UTRAN-FDD, 3GPP-E-UTRAN-TDD,ADSL, ADSL2, ADSL2+, RADSL, SDSL, HDSL, HDSL2, G.SHDSL, VDSL, IDSL,3GPP2-1X, 3GPP2-1X-HRPD, 3GPP2-UMB, DOCSIS, IEEE-802.3, IEEE-802.3a,IEEE-802.3e, IEEE-802.3i, IEEE-802.3j, IEEE-802.3u, IEEE-802.3ab,IEEE-802.3ae, IEEE-802.3ak, IEEE-802.3aq, IEEE-802.3an, IEEE-802.3y,IEEE-802.3z, IEEE-802.3y, 3GPP-GERAN, 3GPP-UTRAN, 3GPP-E-UTRAN,3GPP-WLAN, 3GPP-GAN, or 3GPP-HSPA. In some cases, however, other accesstechnologies, classes or types may be employed.

Another example method of transferring IUT controller function from onedevice to another includes receiving in a Session Initiation Protocol(SIP) message an indication of the transfer of the IUT:Controllerfunction. The indication of the transfer of the IUT:Controller functionmay be indicated using a Media Feature Tag. The Media Feature Tag may becontained in an Accept-Contact Header. The Session Initiation Protocol(SIP) message may be one or more of a SIP INVITE request, a SIPRe-INVITE request, a SIP UPDATE request, a SIP PRACK request, a SIPREFER request, a SIP PUBLISH request, a SIP MESSAGE request, a SIPSUBSCRIBE request, a SIP NOTIFY request, a SIP OPTIONS request, or a SIPINFO Request. The Media Feature Tag may be contained in anAccept-Contact Header is itself contained within a Refer-To header. Themethod may include sending in response an indication of one ofSuccessful IUT Transfer, and Unsuccessful IUT Transfer. The indicationmay be contained in one of a SIP Response, a SIP UPDATE request, a SIPPRACK request, a SIP NOTIFY Request, a SIP PUBLISH Request, a SIPMESSAGE Request, a SIP OPTIONS request, and a SIP INFO Request. Theindication may be one of a Media feature tag in a Contact header, withinthe body of a SIP request or SIP response, within a SIPfrag in a body ofa SIP request or SIP response, or encoded in XML format. The method mayinclude performing the Active IUT Controller function for thecollaborative session.

The present system may be further configured to direct a SIP REQUESTover a specific access application. An example method for identifying aregistration flow over an access network includes providing in aP-Access-Network-Info header of a Session Initiation Protocol (SIP)REGISTER request an identifier that identifies the access type of theaccess network that SIP REGISTER request is transported over, andproviding in the Contact header of a Session Initiation Protocol (SIP)REGISTER request a Media Feature Tag containing a value that uniquelyidentifies the registration flow over all other registrations by thesame device. The Media Feature Tag may contain a value derived from the“reg-id” contact header parameter included in the SIP REGISTER request.The Media Feature Tag may contain a value that is a text string. TheMedia Feature Tag contains a value that is a text string input by theuser.An example method of identifying a registration flow over an accessnetwork includes obtaining from a P-Access-Network-Info header of aSession Initiation Protocol (SIP) REGISTER request an identifier thatidentifies the access type or access class of the access network thatSIP REGISTER request is transported over, obtaining from a Contactheader of a Session Initiation Protocol (SIP) REGISTER request a MediaFeature Tag containing a value that uniquely identifies the registrationflow over all other registrations by the same device, and associatingthe access type or access class with the value from the Media FeatureTag. The contents of the Session Initiation Protocol (SIP) REGISTERrequest may be obtained using at least one of the body of a receivedthird party REGISTER request, the P-Access-Network-Info header in areceived third party REGISTER request, and the registration eventpackage within the body of a SIP NOTIFY request. The method may includereceiving a SIP request or generating a SIP request, determining thatthe SIP request is to be routed over a particular access leg identifiedby an access type or access class value, retrieving the Media FeatureTag value associated with access type or access class value, andincluding in the SIP request in an Accept-Contact header the retrievedMedia Feature Tag value. The SIP request may be one of a SIP INVITERequest, a SIP Re-INVITE request, a SIP UPDATE request, a SIP PRACKrequest, a SIP REFER request, a SIP PUBLISH request, a SIP MESSAGErequest, a SIP SUBSCRIBE request, a SIP OPTIONS request, and a SIP INFORequest.

An example method of identifying a registration flow over an accessnetwork that a request is to be sent over includes providing in anAccept-Contact header of a SIP Request a Media Feature Tag containing avalue that uniquely identifies a registration flow of a device. TheMedia Feature Tag may contain a value that is a text string. The MediaFeature Tag may contain a value that is a text string input by the user.The SIP request may be one of a SIP INVITE Request, a SIP RE-INVITErequest, a SIP UPDATE request, a SIP PRACK request, a SIP REFER request,a SIP PUBLISH request, a SIP MESSAGE request, a SIP SUBSCRIBE request, aSIP OPTIONS request, and a SIP INFO Request. The Media Feature Tag maybe contained in an Accept-Contact Header is itself contained within aRefer-To header.

FIG. 14 is an illustration of an alternative message flow formedia/controller functionality transfer to another UE withinCollaborative Session using Gm reference point. The message flowillustrated in FIG. 14, shows an example method for transferring mediaand IUT Controller functionality from UE-1 to UE-2, where the incomingsession is delivered over the Gm reference point and the media isestablished via CS network. In the example, it is assumed that UE-1 andUE-2 belong to the same subscriber (i.e. the same subscription set),Interworking entities correspond to MSC enhanced for ICS, and followstermination procedures with CS media using Gm reference point shown inTS 23.292. In this example, when the interworking entities correspond toMSC Server and MGCF the CS bearer setup procedures may follow the steps11-17 in the FIG. 7.4.2.2.2-2 the TS 23.292.

Referring to FIG. 14, in step 1401 UE 1 decides to transfer the Media-Aand collaborative session control to UE 2 and sends IMS entities atransfer request indicating that the current collaborative sessioncontrol and Media-A is to be transferred to UE 2. In step 1402 the IMSentities forward the transfer request to the SCC AS and in step 1403 theSCC AS indentifies the transfer request, verifies that the UE-2 isallowed and capable to act as a controller, performs T-ADS based on theUE-2 capability, user preference and/or policy in the network andchooses the CS domain for setup of the Media-A. If UE-2 is not allowedto act as a controller or the transfer request can't be performedsuccessfully the SCC AS rejects the request with the reason and stopfollowing the steps below.

Still referring to FIG. 14, in step 1404 the SCC AS generates and sendsIMS entities an INVITE request indicating that the Media-A andcollaborative session control and that the UE-2 to initiate the CSbearer establishment procedure as shown in TS 23.292. In step 1405 theIMS entities forward the received INVITE request to the UE-2, and instep 1406 the UE-2 sends a CS call setup message to the Interworkingentities. In step 1407 the Interworking entities respond with a callproceeding message and begins to set up the CS Bearer Control SignallingPath, and in steps 1408 and 1409 the Interworking entities send anINVITE towards the SCC AS via IMS entities. In step 1410 the UE-2,Interworking entities and SCC AS complete the setup of the CS BearerControl Signalling Path. The Collaborative Session control between UE 2and the SCC AS is established. UE 2 becomes the controller UE for theestablished Collaborative Session. In step 1411 media-A between UE 2 andremote party is established. The remote leg is updated accordingly. Instep 1412, after the successful transfer of the Collaborative Sessioncontrol and Media-A onto the UE 2, the SCC AS sends the IMS entities anIUT transfer result message, and in step 1413 the IMS entities forwardthe IUT transfer result message to the UE-1. Finally, in step 1414 theprevious Media-A and Collaborative Session control is released. UE 1becomes a controlee UE.

FIG. 15 is an illustration of an alternative message flow formedia/controller functionality transfer to another UE withinCollaborative Session using the I1 reference point. The message flowillustrated in FIG. 15, shows an example method for transferring IUTController functionality from UE-1 to UE-2, where the incoming sessionis delivered over the I1 reference point and the media is establishedvia CS network. In this example, it is assumed that UE-1 and UE-2 belongto the same subscriber (i.e. the same subscription set), Interworkingentities correspond to MSC enhanced for ICS, and follows terminationprocedures with CS media using I1 reference point shown in TS 23.292. Inthis example, when the interworking entities correspond to MSC Serverand MGCF the CS bearer setup procedures follow the steps 11-17 in theFIG. 7.4.2.2.2-2 of the TS 23.292.

Referring to FIG. 15, in step 1501, UE 1 decides to transfer the Media-Aand collaborative session control to UE 2 and sends IMS entities atransfer request indicating that the current collaborative sessioncontrol and Media-A is to be transferred to UE 2. In step 1502 the IMSentities forward the transfer request to the SCC AS and in step 1503 theSCC AS indentifies the transfer request, verifies that the UE-2 isallowed and capable to act as a controller, performs T-ADS based on theUE-2 capability, user preference and/or policy in the network andchooses the CS domain for setup of the Media-A. If UE-2 is not allowedto act as a controller or the transfer request can't be performedsuccessfully the SCC AS rejects the request with the reason and stopfollowing the steps below. In step 1504 the SCC AS generates and sendsUE-2 an incoming call request via I1 reference point indicating that theUE-2 to initiate the CS bearer establishment procedure and that thecollaborative session control and Media-A to be transferred to UE-2, asshown in TS 23.292.

Still referring to FIG. 15, in step 1505the UE-2 sends a CS call setupmessage to the Interworking entities and in step 1506 the Interworkingentities respond with a call proceeding message and begins to set up theCS Bearer Control Signalling Path. In steps 1507 and 1508 theInterworking entities send an INVITE towards the SCC AS via IMSentities, and in step 1509 the UE-2, Interworking entities and SCC AScomplete the setup of the CS Bearer Control Signaling Path. TheCollaborative Session control between UE 2 and the SCC AS isestablished. UE 2 becomes the controller UE for the establishedCollaborative Session. In step 1510 media-A between UE 2 and remoteparty is established. The remote leg is updated accordingly. In step1511, after the successful transfer of the Collaborative Session controland Media-A onto the UE 2, the SCC AS sends the IMS entities an IUTtransfer result message. In step 1512 the IMS entities forward the IUTtransfer result message to the UE-1, and in step 1513 the previousMedia-A and Collaborative Session control is released. UE 1 becomes acontrolee UE.

FIG. 16 is an illustration of an alternative message flow for ControllerInitiated ongoing session information transfer. In the example shown inFIG. 16, UE-1, UE-2 and UE-3 may be under the same user subscription.There is one session with Media—A between UE-2 and Remote Party andanother session with Media—B between UE-3 and Remote Party. FIG. 16presents an information flow of UE-1 requesting all ongoing sessionstate information for the user's IUT UEs.

Referring to FIG. 16, in step 1601 UE-1 sends the SCC AS a request onongoing session state information for the user's IUT UEs. The requestmay include what information is to be obtained in the response. Theinformation may include the ongoing sessions for the user's IUT UEs, themedia type per an ongoing session, and/or the source UE and the targetUE per an ongoing session. In step 1602 the SCC AS checks all ongoingsessions for the user's IUT UEs and filters the requested informationi.e. there is one session A with media type A between UE-2 and RemoteParty and another session B with media type B between UE-3 and RemoteParty. In step 1603 the SCC AS sends the UE-1 a response on all ongoingsession state information on UE-2 and UE-3.

In implementations of the present system where the SCC AS serves aterminating ICS UE and receives an initial SIP INVITE request due toinitial filter criteria and the T-ADS results in choosing to delivermedia in the PS domain, the SCC AS can act as a B2BUA. If multiplecontacts are registered in the PS domain and the T-ADS chooses toestablish different media types using different IP-CANs, the SCC AS can,for each selected PS domain IP-CAN, create a SIP INVITE request inaccordance with 3GPP TS24.229. The SIP INVITE request may include i) anAccept-Contact header containing the media feature tag g.3gpp.icsflowcontaining the value associated at registration with the access-type oraccess-class of the selected PS domain IP-CAN and the media feature tagg.3gpp.ics containing the value “principal” along with the parameters“require” and “explicit”, and ii) if an existing leg for this sessionalready exists or is in the process of being established between the SCCAS and the ICS UE using a different IP-CAN, a Target-Dialog headercontaining the dialog parameters for that existing dialog between theSCC AS and the ICS UE (the SCC AS SCC AS may include a Target-Dialogheader in the SIP INVITE request so that the ICS UE can correlatedifferent requests as part of the same session), and iii) an SDP for themedia type(s) selected to be established using this IP-CAN.

If multiple contacts are registered in the PS domain and the T-ADSchooses to establish all the media types over the same IP-CAN, the SCCAS may create a SIP INVITE request in accordance with 3GPP TS24.229 andmay include in the request i) an Accept-Contact header containing themedia feature tag g.3gpp.icsflow containing the value associated atregistration with the access-type or access-class of the selected PSdomain IP-CAN and the media feature tag g.3gpp.ics containing the value“principal” along with the parameters “require” and “explicit”, ii) ifan existing leg for this session already exists or is in the process ofbeing established between the SCC AS and the ICS UE using a differentIP-CAN, a Target-Dialog header containing the dialog parameters for thatexisting dialog between the SCC AS and the ICS UE (the SCC AS SCC AS mayinclude a Target-Dialog header in the SIP INVITE request so that the ICSUE can correlate different requests as part of the same session), andiii) an SDP for all the media types contained in the initial SIP INVITErequest.

If only a single contact is registered in the PS domain, the SCC AS maycreate a SIP INVITE request in accordance with 3GPP TS24.229 and mayinclude in the request i)an Accept-Contact header containing the mediafeature tag g.3gpp.ics containing the value “principal” along with theparameters “require” and “explicit”, and ii) an SDP for all the mediatypes contained in the initial SIP INVITE request.

Referring now to FIG. 17, a wireless communications system including anembodiment of an exemplary UE 1700 is illustrated. The UE is operablefor implementing aspects of the disclosure, but the disclosure shouldnot be limited to these implementations. Though illustrated as a mobilephone, the UE may take various forms including a wireless handset, apager, a personal digital assistant (PDA), a portable computer, a tabletcomputer, a laptop computer, smartphones, printers, fax machines,televisions, set top boxes, and other video display devices, home audioequipment and other home entertainment systems, home monitoring andcontrol systems (e.g., home monitoring, alarm systems and climatecontrol systems), and enhanced home appliances such as computerizedrefrigerators. Many suitable devices combine some or all of thesefunctions. In some embodiments of the disclosure, the UE 1700 is not ageneral purpose computing device like a portable, laptop or tabletcomputer, but rather is a special-purpose communications device such asa mobile phone, a wireless handset, a pager, a PDA, or atelecommunications device installed in a vehicle. The UE 1700 may alsobe a device, include a device, or be included in a device that hassimilar capabilities but that is not transportable, such as a desktopcomputer, a set-top box, or a network node. The UE 1700 may supportspecialized activities such as gaming, inventory control, job control,and/or task management functions, and so on.

The UE 1700 includes a display 702. The UE 1700 also includes atouch-sensitive surface, a keyboard or other input keys generallyreferred as 704 for input by a user. The keyboard may be a full orreduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY, andsequential types, or a traditional numeric keypad with alphabet lettersassociated with a telephone keypad. The input keys may include atrackwheel, an exit or escape key, a trackball, and other navigationalor functional keys, which may be inwardly depressed to provide furtherinput function. The UE 1700 may present options for the user to select,controls for the user to actuate, and/or cursors or other indicators forthe user to direct.

The UE 1700 may further accept data entry from the user, includingnumbers to dial or various parameter values for configuring theoperation of the UE 1700. The UE 1700 may further execute one or moresoftware or firmware applications in response to user commands. Theseapplications may configure the UE 1700 to perform various customizedfunctions in response to user interaction. Additionally, the UE 1700 maybe programmed and/or configured over-the-air, for example from awireless base station, a wireless access point, or a peer UE 1700.

Among the various applications executable by the UE 1700 is a webbrowser, which enables the display 702 to show a web page. The web pagemay be obtained via wireless communications with a wireless networkaccess node, a cell tower, a peer UE 1700, or any other wirelesscommunication network or system 1702. The network 1702 is coupled to awired network 1704, such as the Internet. Via the wireless link and thewired network, the UE 1700 has access to information on various servers,such as a server 1706. The server 1706 may provide content that may beshown on the display 702. Alternately, the UE 1700 may access thenetwork 1702 through a peer UE 1700 acting as an intermediary, in arelay type or hop type of connection.

FIG. 18 shows a block diagram of the UE 1700. While a variety of knowncomponents of UAs 1700 are depicted, in an embodiment a subset of thelisted components and/or additional components not listed may beincluded in the UE 1700. The UE 1700 includes a digital signal processor(DSP) 1802 and a memory 1804. As shown, the UE 1700 may further includean antenna and front end unit 1806, a radio frequency (RF) transceiver1808, an analog baseband processing unit 1810, a microphone 1812, anearpiece speaker 1814, a headset port 1816, an input/output interface1818, a removable memory card 1820, a universal serial bus (USB) port1822, a short range wireless communication sub-system 1824, an alert1826, a keypad 1828, a liquid crystal display (LCD), which may include atouch sensitive surface 1830, an LCD controller 1832, a charge-coupleddevice (CCD) camera 1834, a camera controller 1836, and a globalpositioning system (GPS) sensor 1838. In an embodiment, the UE 1700 mayinclude another kind of display that does not provide a touch sensitivescreen. In an embodiment, the DSP 1802 may communicate directly with thememory 1804 without passing through the input/output interface 1818.

The DSP 1802 or some other form of controller or central processing unitoperates to control the various components of the UE 1700 in accordancewith embedded software or firmware stored in memory 1804 or stored inmemory contained within the DSP 1802 itself. In addition to the embeddedsoftware or firmware, the DSP 1802 may execute other applications storedin the memory 1804 or made available via information carrier media suchas portable data storage media like the removable memory card 1820 orvia wired or wireless network communications. The application softwaremay comprise a compiled set of machine-readable instructions thatconfigure the DSP 1802 to provide the desired functionality, or theapplication software may be high-level software instructions to beprocessed by an interpreter or compiler to indirectly configure the DSP1802.

The antenna and front end unit 1806 may be provided to convert betweenwireless signals and electrical signals, enabling the UE 1700 to sendand receive information from a cellular network or some other availablewireless communications network or from a peer UE 1700. In anembodiment, the antenna and front end unit 1806 may include multipleantennas to support beam forming and/or multiple input multiple output(MIMO) operations. As is known to those skilled in the art, MIMOoperations may provide spatial diversity which can be used to overcomedifficult channel conditions and/or increase channel throughput. Theantenna and front end unit 1806 may include antenna tuning and/orimpedance matching components, RF power amplifiers, and/or low noiseamplifiers.

The RF transceiver 1808 provides frequency shifting, converting receivedRF signals to baseband and converting baseband transmit signals to RF.In some descriptions a radio transceiver or RF transceiver may beunderstood to include other signal processing functionality such asmodulation/demodulation, coding/decoding, interleaving/deinterleaving,spreading/despreading, inverse fast Fourier transforming (IFFT)/fastFourier transforming (FFT), cyclic prefix appending/removal, and othersignal processing functions. For the purposes of clarity, thedescription here separates the description of this signal processingfrom the RF and/or radio stage and conceptually allocates that signalprocessing to the analog baseband processing unit 1810 and/or the DSP1802 or other central processing unit. In some embodiments, the RFtransceiver 1808, portions of the antenna and front end 1806, and theanalog baseband processing unit 1810 may be combined in one or moreprocessing units and/or application specific integrated circuits(ASICs).

The analog baseband processing unit 1810 may provide various analogprocessing of inputs and outputs, for example analog processing ofinputs from the microphone 1812 and the headset 1816 and outputs to theearpiece 1814 and the headset 1816. To that end, the analog basebandprocessing unit 1810 may have ports for connecting to the built-inmicrophone 1812 and the earpiece speaker 1814 that enable the UE 1700 tobe used as a cell phone. The analog baseband processing unit 1810 mayfurther include a port for connecting to a headset or other hands-freemicrophone and speaker configuration. The analog baseband processingunit 1810 may provide digital-to-analog conversion in one signaldirection and analog-to-digital conversion in the opposing signaldirection. In some embodiments, at least some of the functionality ofthe analog baseband processing unit 1810 may be provided by digitalprocessing components, for example by the DSP 1802 or by other centralprocessing units.

The DSP 1802 may perform modulation/demodulation, coding/decoding,interleaving/deinterleaving, spreading/despreading, inverse fast Fouriertransforming (IFFT)/fast Fourier transforming (FFT), cyclic prefixappending/removal, and other signal processing functions associated withwireless communications. In an embodiment, for example in a codedivision multiple access (CDMA) technology application, for atransmitter function the DSP 1802 may perform modulation, coding,interleaving, and spreading, and for a receiver function the DSP 1802may perform despreading, deinterleaving, decoding, and demodulation. Inanother embodiment, for example in an orthogonal frequency divisionmultiplex access (OFDMA) technology application, for the transmitterfunction the DSP 1802 may perform modulation, coding, interleaving,inverse fast Fourier transforming, and cyclic prefix appending, and fora receiver function the DSP 1802 may perform cyclic prefix removal, fastFourier transforming, deinterleaving, decoding, and demodulation. Inother wireless technology applications, yet other signal processingfunctions and combinations of signal processing functions may beperformed by the DSP 1802.

The DSP 1802 may communicate with a wireless network via the analogbaseband processing unit 1810. In some embodiments, the communicationmay provide Internet connectivity, enabling a user to gain access tocontent on the Internet and to send and receive e-mail or text messages.The input/output interface 1818 interconnects the DSP 1802 and variousmemories and interfaces. The memory 1804 and the removable memory card1820 may provide software and data to configure the operation of the DSP1802. Among the interfaces may be the USB interface 1822 and the shortrange wireless communication sub-system 1824. The USB interface 1822 maybe used to charge the UE 1700 and may also enable the UE 1700 tofunction as a peripheral device to exchange information with a personalcomputer or other computer system. The short range wirelesscommunication sub-system 1824 may include an infrared port, a Bluetoothinterface, an IEEE 802.11 compliant wireless interface, or any othershort range wireless communication sub-system, which may enable the UE1700 to communicate wirelessly with other nearby mobile devices and/orwireless base stations.

The input/output interface 1818 may further connect the DSP 1802 to thealert 1826 that, when triggered, causes the UE 1700 to provide a noticeto the user, for example, by ringing, playing a melody, or vibrating.The alert 1826 may serve as a mechanism for alerting the user to any ofvarious events such as an incoming call, a new text message, and anappointment reminder by silently vibrating, or by playing a specificpre-assigned melody for a particular caller.

The keypad 1828 couples to the DSP 1802 via the interface 1818 toprovide one mechanism for the user to make selections, enterinformation, and otherwise provide input to the UE 1700. The keyboard1828 may be a full or reduced alphanumeric keyboard such as QWERTY,Dvorak, AZERTY and sequential types, or a traditional numeric keypadwith alphabet letters associated with a telephone keypad. The input keysmay include a trackwheel, an exit or escape key, a trackball, and othernavigational or functional keys, which may be inwardly depressed toprovide further input function. Another input mechanism may be the LCD1830, which may include touch screen capability and also display textand/or graphics to the user. The LCD controller 1832 couples the DSP1802 to the LCD 1830.

The CCD camera 1834, if equipped, enables the UE 1700 to take digitalpictures. The DSP 1802 communicates with the CCD camera 1834 via thecamera controller 1836. In another embodiment, a camera operatingaccording to a technology other than Charge Coupled Device cameras maybe employed. The GPS sensor 1838 is coupled to the DSP 1802 to decodeglobal positioning system signals, thereby enabling the UE 1700 todetermine its position. Various other peripherals may also be includedto provide additional functions, e.g., radio and television reception.

FIG. 19 illustrates a software environment 1902 that may be implementedby the DSP 1802. The DSP 1802 executes operating system drivers 1904that provide a platform from which the rest of the software operates.The operating system drivers 1904 provide drivers for the UA hardwarewith standardized interfaces that are accessible to applicationsoftware. The operating system drivers 1904 include applicationmanagement services (“AMS”) 1906 that transfer control betweenapplications running on the UE 1700. Also shown in FIG. 19 are a webbrowser application 1908, a media player application 1910, and Javaapplets 1912. The web browser application 1908 configures the UE 1700 tooperate as a web browser, allowing a user to enter information intoforms and select links to retrieve and view web pages. The media playerapplication 1910 configures the UE 1700 to retrieve and play audio oraudiovisual media. The Java applets 1912 configure the UE 1700 toprovide games, utilities, and other functionality. A component 1914might provide functionality described herein.

The UE 1700, access device, and other components described above mightinclude a processing component that is capable of executing instructionsrelated to the actions described above. FIG. 20 illustrates an exampleof a system 2000 that includes a processing component 2010 suitable forimplementing one or more embodiments disclosed herein. In addition tothe processor 2010 (which may be referred to as a central processor unit(CPU or DSP), the system 2000 might include network connectivity devices2020, random access memory (RAM) 2030, read only memory (ROM) 2040,secondary storage 2050, and input/output (I/O) devices 2060. In someembodiments, a program for implementing the determination of a minimumnumber of HARQ process IDs may be stored in ROM 2040. In some cases,some of these components may not be present or may be combined invarious combinations with one another or with other components notshown. These components might be located in a single physical entity orin more than one physical entity. Any actions described herein as beingtaken by the processor 2010 might be taken by the processor 2010 aloneor by the processor 2010 in conjunction with one or more componentsshown or not shown in the drawing.

The processor 2010 executes instructions, codes, computer programs, orscripts that it might access from the network connectivity devices 2020,RAM 2030, ROM 2040, or secondary storage 2050 (which might includevarious disk-based systems such as hard disk, floppy disk, or opticaldisk). While only one processor 2010 is shown, multiple processors maybe present. Thus, while instructions may be discussed as being executedby a processor, the instructions may be executed simultaneously,serially, or otherwise by one or multiple processors. The processor 2010may be implemented as one or more CPU chips.

The network connectivity devices 2020 may take the form of modems, modembanks, Ethernet devices, universal serial bus (USB) interface devices,serial interfaces, token ring devices, fiber distributed data interface(FDDI) devices, wireless local area network (WLAN) devices, radiotransceiver devices such as code division multiple access (CDMA)devices, global system for mobile communications (GSM) radio transceiverdevices, worldwide interoperability for microwave access (WiMAX)devices, and/or other well-known devices for connecting to networks.These network connectivity devices 2020 may enable the processor 2010 tocommunicate with the Internet or one or more telecommunications networksor other networks from which the processor 2010 might receiveinformation or to which the processor 2010 might output information.

The network connectivity devices 2020 might also include one or moretransceiver components 2025 capable of transmitting and/or receivingdata wirelessly in the form of electromagnetic waves, such as radiofrequency signals or microwave frequency signals. Alternatively, thedata may propagate in or on the surface of electrical conductors, incoaxial cables, in waveguides, in optical media such as optical fiber,or in other media. The transceiver component 2025 might include separatereceiving and transmitting units or a single transceiver. Informationtransmitted or received by the transceiver 2025 may include data thathas been processed by the processor 2010 or instructions that are to beexecuted by processor 2010. Such information may be received from andoutputted to a network in the form, for example, of a computer databaseband signal or signal embodied in a carrier wave. The data may beordered according to different sequences as may be desirable for eitherprocessing or generating the data or transmitting or receiving the data.The baseband signal, the signal embedded in the carrier wave, or othertypes of signals currently used or hereafter developed may be referredto as the transmission medium and may be generated according to severalmethods well known to one skilled in the art.

The RAM 2030 might be used to store volatile data and perhaps to storeinstructions that are executed by the processor 2010. The ROM 2040 is anon-volatile memory device that typically has a smaller memory capacitythan the memory capacity of the secondary storage 2050. ROM 2040 mightbe used to store instructions and perhaps data that are read duringexecution of the instructions. Access to both RAM 2030 and ROM 2040 istypically faster than to secondary storage 2050. The secondary storage2050 is typically comprised of one or more disk drives or tape drivesand might be used for non-volatile storage of data or as an over-flowdata storage device if RAM 2030 is not large enough to hold all workingdata. Secondary storage 2050 may be used to store programs that areloaded into RAM 2030 when such programs are selected for execution.

The I/O devices 2060 may include liquid crystal displays (LCDs), touchscreen displays, keyboards, keypads, switches, dials, mice, track balls,voice recognizers, card readers, paper tape readers, printers, videomonitors, or other well-known input devices. Also, the transceiver 2025might be considered to be a component of the I/O devices 2060 instead ofor in addition to being a component of the network connectivity devices2020. Some or all of the I/O devices 2060 may be substantially similarto various components depicted in the previously described drawing ofthe UE 1700, such as the display and the input.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated in another systemor certain features may be omitted, or not implemented.

Also, techniques, systems, subsystems and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as coupled or directly coupled orcommunicating with each other may be indirectly coupled or communicatingthrough some interface, device, or intermediate component, whetherelectrically, mechanically, or otherwise. Other examples of changes,substitutions, and alterations are ascertainable by one skilled in theart and could be made without departing from the spirit and scopedisclosed herein.

1. A method to transfer control, comprising: receiving a request totransfer control of a collaborative session from a first user equipment(UE); sending a request for the transfer of control of the collaborativesession in response to the received request to a second UE; receiving,in response to the sent request to the second UE, an indication ofacceptance of the transfer of control of the collaborative session;sending a notification of status to the first UE of the control of thecollaborative session in response to receiving, from the second UE, theindication of acceptance.
 2. The method of claim 1, wherein the receivedresponse is encoded as session initiation protocol (SIP).
 3. The methodof claim 2, wherein the SIP message is a SIP REFER message.
 4. Themethod of claim 1, further comprising sending a NOTIFY messageindicating success in response to receiving the request to transfercontrol.
 5. The method of claim 1, wherein the message requestingtransfer of control of a collaborative session also comprises a requestfor media transfer.
 6. A network node, comprising: a processor, theprocessor being configured to: receive a request to transfer control ofa collaborative session from a first user equipment (UE); send a requestfor the transfer of control of the collaborative session in response tothe received request to a second UE; receive, in response to the sentrequest to the second UE, an indication of acceptance of the transfer ofcontrol of the collaborative session; send a notification of status tothe first UE of the control of the collaborative session in response toreceiving, from the second UE, the indication of acceptance.
 7. Thenetwork node of claim 6, wherein the received response is encoded asSIP.
 8. The network node of claim 7, wherein the SIP message is a SIPREFER message.
 9. The network node of claim 6, further comprisingsending a NOTIFY message indicating success in response to receiving therequest to transfer control.
 10. The network node of claim 6, whereinthe message requesting transfer of control of a collaborative sessionalso comprises a request for media transfer.
 11. The network node ofclaim 6, wherein the network node includes a service consistency andcontinuity application server (SCC AS).
 12. A user equipment (UE),comprising: a processor, the processor being configured to: transmit arequest to transfer control of a collaborative session from a first userequipment (UE); receive a notification of status of the control of thecollaborative session.
 13. The UE of claim 12, wherein the notificationof status includes a NOTIFY message.
 14. The UE of claim 12, wherein themessage requesting transfer of control of a collaborative session alsocomprises a request for media transfer.